transcripts-mcp
AGENTS.md8 starsChanged 2 months agoMITView on GitHub
This is a deepsec scanning workspace. Each registered project has its own setup prompt at data/<id>/SETUP.md — open the relevant one when asked to set a project up. - Set up or resume a project: run pnpm deepsec setup. For a scaffold-only/manual setup, read data/<id>/SETUP.md and follow it. - Add a new project: run deepsec init-project <root> — it scaffolds data/<id>/ and prints/writes the setup prompt for the new project. - Write a custom matcher (only after a real true-positive…
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mangue-dev/minddyword for word, first seen Nov 2, 2026
Other versions1 project uses a version of this.
Word for word · 1
- mangue-dev/minddy★ 1100% same
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,542 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.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/010-workflow.mdcCursor rule
- .cursor/rules/020-codebase-structure.mdcCursor rule
- .cursor/rules/030-coding-style.mdcCursor rule
- .cursor/rules/031-never-use-any.mdcCursor rule
- .cursor/rules/032-import-rules.mdcCursor rule
- .cursor/rules/050-testing.mdcCursor rule
- .cursor/rules/070-comments-defensive-programming.mdcCursor rule
- .cursor/rules/080-ai-interaction.mdcCursor rule
- .cursor/rules/090-changesets.mdcCursor rule
- .cursor/rules/095-calldiff.mdcCursor rule
- .cursor/rules/990-cursor-rule-editing-workaround.mdcCursor rule
- .cursor/rules/999-mdc-format.mdcCursor rule
- adversarial-reviewSkill
- agent-browserSkill
- calldiffSkill
- changesetSkill
- commitSkill
- deslopSkill
- fix-prSkill
- git-conventionsSkill
- humanizerSkill
- improve-codebase-architectureSkill
- logging-best-practicesSkill
- opensrcSkill
- rebaseSkill
- recomposing-commitsSkill
- security-reviewSkill
- show-meSkill
- simplifySkill
- thermo-nuclear-code-quality-reviewSkill
- wait-whatSkill
- writing-for-agentsSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Set up or resume a project: run pnpm deepsec setup. For a scaffold-only/manual setup, read data/<id>/SETUP.md and follow it.
- Very specific: line 11
Add a new project: run deepsec init-project <root> — it scaffolds data/<id>/ and prints/writes the setup prompt for the new project.
≈ “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 setup
This is a deepsec scanning workspace. Each registered project has its
own setup prompt at data/<id>/SETUP.md — open the relevant one when
asked to set a project up.
Common tasks
- Set up or resume a project: run
pnpm deepsec setup. For a scaffold-only/manual setup, readdata/<id>/SETUP.mdand follow it. - Add a new project: run
deepsec init-project <root>— it scaffoldsdata/<id>/and prints/writes the setup prompt for the new project. - Write a custom matcher (only after a real true-positive shows you
a pattern worth keeping): read
node_modules/deepsec/dist/docs/writing-matchers.md.
Reference
The deepsec skill is at node_modules/deepsec/SKILL.md (after
pnpm install). The full docs ship at
node_modules/deepsec/dist/docs/.
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.