ctf-kit
AGENTS.md12 starsChanged 9 months agoMITView on GitHub
This project uses bd (beads) for issue tracking. Run bd onboard to get started. When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds. MANDATORY WORKFLOW: CRITICAL RULES: - Work is NOT complete until git push succeeds - NEVER stop before pushing - that leaves work stranded locally - NEVER say "ready to push when you are" - YOU must push - If push fails, resolve and retry until it succeeds
- Commits and pushes
33 other projects use a version of this; 1 new project in the last 4 weeks, against 1 the 4 before.
Adopted by
Steady: 1 new project took it in the last 4 weeks, 1× the 4 weeks before.thin data
Most recently taken up by
- olgasafonova/gleif-mcp-serverword for word, first seen Nov 8, 2026
- olgasafonova/mediawiki-mcp-serverword for word, first seen Nov 7, 2026
- Dicoangelo/claude-command-centerword for word, first seen Oct 20, 2026
- jeremylongshore/waygate-mcpword for word, first seen Oct 13, 2026
- Michael-A-Kuykendall/crabcameraword for word, first seen Oct 9, 2026
- Michael-A-Kuykendall/muxideword for word, first seen Oct 9, 2026
Other versions33 projects use a version of this.
Word for word · 33
- CloakHQ/CloakBrowser-Manager★ 997100% same
- skygazer42/Weaver★ 185100% same
- Michael-A-Kuykendall/crabcamera★ 165100% same
- OmidZamani/dspy-skills★ 123100% same
- block/codecrucible★ 120100% same
- dbinky/Pommel★ 110100% same
- yazinsai/claude-code-remote★ 101100% same
- MotWakorb/enhancedchannelmanager★ 89100% same
- Michael-A-Kuykendall/muxide★ 80100% same
- jeremylongshore/excel-analyst-pro-skill-md★ 60100% same
23 more not listed
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
File issues for remaining work: - Create issues for anything that needs follow-up
- Distinctive: line 32
Verify: - All changes committed AND pushed
- Distinctive: line 37
NEVER stop before pushing - that leaves work stranded locally
- Distinctive: line 38
NEVER say "ready to push when you are" - YOU must push
- Distinctive: line 39
If push fails, resolve and retry until it succeeds
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Instructions
This project uses bd (beads) for issue tracking. Run bd onboard to get started.
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --status in_progress # Claim work
bd close <id> # Complete work
bd sync # Sync with gitLanding the Plane (Session Completion)
When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.
MANDATORY WORKFLOW:
- File issues for remaining work - Create issues for anything that needs follow-up
- Run quality gates (if code changed) - Tests, linters, builds
- Update issue status - Close finished work, update in-progress items
- PUSH TO REMOTE - This is MANDATORY:
git pull --rebase bd sync git push git status # MUST show "up to date with origin" - Clean up - Clear stashes, prune remote branches
- Verify - All changes committed AND pushed
- Hand off - Provide context for next session
CRITICAL RULES:
- Work is NOT complete until
git pushsucceeds - NEVER stop before pushing - that leaves work stranded locally
- NEVER say "ready to push when you are" - YOU must push
- If push fails, resolve and retry until it succeeds
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

