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 instructions/duthaho/skillhub/agents-mdgit clone --depth 1 https://github.com/duthaho/skillhubWhat 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 | $0.01118 | $0.01118 |
| Opus 5 | $0.00559 | $0.00559 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
Grade A, and why
skillhub AGENTS.md 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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
What this is
A collection of Claude Code skills (.claude/skills/<name>/SKILL.md) for
research, daily work, and a coding loop. No application code, no build system —
every skill is a markdown file with YAML frontmatter that Claude Code loads.
Entry point for a reader is README.md; entry point for a user is any skill's
slash command (e.g. /pulse).
Build, test, run
There is nothing to compile and no test suite — this is a docs-only repo. Validation is by inspection:
- Validate before committing:
python3 scripts/validate-skills.py— frontmatter (name= folder, no clash with harness built-ins,descriptionpresent, hard 1024-char limit with a soft WARN above 950), marketplace coverage both ways, README rows, references/ integrity.--descriptionsdumps the model-visible trigger surface (skills withdisable-model-invocation: trueexcluded) for the eval below. - Reworded a description? Re-run the trigger eval per
evals/README.md(fresh judge sub-agent overevals/triggers.json); the authoring lint is §3 of that file. A description is a skill's only trigger surface. - Install (from
README.md):/plugin marketplace add duthaho/skillhub(plugins defined in.claude-plugin/marketplace.json— a new skill must be added to a plugin'sskillslist there too), orcp -r/symlink the folders. - Run a skill by typing its command in Claude Code; skills lean on Claude Code's sub-agents and web tools, no external services.
Architecture
- Each skill is self-contained in
.claude/skills/<name>/. A user may copy one folder alone, so cross-skill conventions (date viadate +%F,out/creation, keyless degradation) are duplicated by design — don't try to factor them into a shared file. - Progressive disclosure via
references/: heavy output templates and design briefs live in.claude/skills/<name>/references/*.md, loaded only when the skill reaches that step (blueprint, jobfit, pulse, refactor, scout, verdict). TheSKILL.mdbody loads on every trigger, so keep it lean. - State model: skills write to
out/<skill>/in whatever project they run in (out/dev/for the coding loop; shipped change folders move toout/dev/archive/). SeeREADME.md"How the memory works". - The coding loop composes:
map→feature/bugfix/refactor→done, withautopilotwrapping the whole loop,scoutfeeding it candidates, andblueprintas map's human-facing sibling.
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.
- 2d ago First seen · 78 lines · 1,118 tokens per session scan A 4c444f9fb12e
skillhub AGENTS.md is an instructions file published in the GitHub repository duthaho/skillhub (9 stars, last pushed 9d ago), licensed MIT. It adds 1,118 tokens to every session, about $0.0056 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 instructions, from other repositories
moo.md CLAUDE.md
Instructions for saadshahd/moo.md, covering claude.md, what this is, conventions, philosophy and model-judgment boundaries.
director-mode-lite copilot-instructions.md
Instructions for claude-world/director-mode-lite: This is a Shell/Markdown toolkit for Claude Code Director Mode. Keep shell scripts POSIX-compatible where possible. Markdown files are the primary deliverable.
claude-code-plugins AGENTS.md
Instructions for DropFan/claude-code-plugins, covering claude code plugins collection, repository structure, plugin management, development guidelines and adding a self-developed plugin.
claude-code-plugins AGENTS.md
AGENTS.md instructions for qte77/claude-code-plugins, covering agent instructions, claude code infrastructure, core rules & ai behavior, decision framework and agent neutrality requirements.
dot-claude-plugins CLAUDE.md
Instructions for and3r817/dot-claude-plugins, covering claude.md, repository overview, core architecture principles, testing commands and run all test suites (master runner).
claude-code-plugins CLAUDE.md
Instructions for DropFan/claude-code-plugins, covering claude code plugins collection, repository structure, plugin management, development guidelines and adding a self-developed plugin.