Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/sananthanarayan/skilldrop/agents-md-generatornpx skills add sananthanarayan/skilldrop --skill agents-md-generatorgit clone --depth 1 https://github.com/sananthanarayan/skilldropWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sananthanarayan/skilldrop/agents-md-generator)<a href="https://agentmods.dev/skills/sananthanarayan/skilldrop/agents-md-generator"><img src="https://agentmods.dev/badge/skills/sananthanarayan/skilldrop/agents-md-generator.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.01763 |
| Opus 5 | $0.00049 | $0.00881 |
| Sonnet 5 | $0.00020 | $0.00353 |
| Haiku 4.5 | $0.00010 | $0.00176 |
Grade A, and why
agents-md-generator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agents-md-generator
Produces the file agents read before the user's prompt. An AGENTS.md is not documentation — it is the context an agent spends on every turn, so a line that changes no decision is a line stolen from the task.
The failure that makes these files worse than useless is an invented command. npm test in a repo with no test script sends every agent down a path that fails, and the agent trusts the file over the filesystem. So the rule this skill is built around: every command traces to evidence in the repo, or it does not appear.
Two modes, chosen by what's already there:
- Generate — no
AGENTS.mdexists. Produce one under the line cap. - Audit — one exists. Score it, name what can't be verified, emit a diff. Never silently rewrite a hand-tuned file.
How to respond
-
Inventory the real command surface before writing anything. Read, in this order:
package.json(scripts),Makefile,pyproject.toml/setup.cfg,Cargo.toml,go.mod,composer.json,.github/workflows/*.yml,justfile,Taskfile.yml, and anyCONTRIBUTING.md. CI workflows are the highest-value source: they contain the commands that actually have to pass.For each command record its provenance — the file and key it came from. Provenance is what makes audit mode possible later.
-
Apply the evidence rule without exception. A command appears only if it traces to a file in the repo. Never infer from ecosystem convention: a Python repo does not necessarily run
pytest, and a repo withjestindevDependenciesmay still have no test script.When a section needs a command that doesn't exist, write the marker, not a guess: ✅ "Test:
[missing: no test script in package.json or CI]" — ❌ "Test:npm test". The marker is useful; the guess is a trap. -
Derive file placement from the actual tree, not from what the framework usually does. Name the directories that exist and what belongs in each. Two or three rows beat a full tree dump.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 81 lines · 98 tokens per session scan A 2acd3dbe91ad
agents-md-generator is a skill published in the GitHub repository sananthanarayan/skilldrop (2 stars, last pushed 22d ago), licensed MIT. It adds 98 tokens to every session and 1,763 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.
team-repair
Re-index OKF v0.2 index.md/log.md files, derive CDR.md, rebuild .skills.json and AGENTS.md in team-ai-directives, migrate v0.1→v0.2 frontmatter, scan for rule conflicts, and verify directive freshness. Use when indexes are inconsistent, orphans are detected, after bulk changes, or for periodic team AI directives…