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/jcottam/agent-resources/agents-mdgit clone --depth 1 https://github.com/jcottam/agent-resourcesWhat 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.00137 | $0.00137 |
| Opus 5 | $0.00068 | $0.00068 |
| Sonnet 5 | $0.00027 | $0.00027 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
agent-resources 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 3d 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.
What it actually says
Agent Resources
This repository contains agent skills and Cursor rules.
Contributing
- Skills live in
skills/<category>/<skill-name>/SKILL.md. - Each
SKILL.mdhas YAML frontmatter withnameanddescription, followed by the skill body in markdown. - When adding a skill, also add it to
.claude-plugin/plugin.jsonand the reference table inREADME.md. - Rules live in
rules/as.mdcfiles with YAML frontmatter (description,globs,alwaysApply). - Keep skills focused on a single concern. Prefer short, composable skills over large monolithic ones.
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.
- 3d ago First seen · 12 lines · 137 tokens per session scan A 1c8e0d9821b0
agent-resources AGENTS.md is an instructions file published in the GitHub repository jcottam/agent-resources (30 stars, last pushed 27d ago), licensed MIT. It adds 137 tokens to every session, about $0.0007 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-30.
Other instructions, from other repositories
loom CLAUDE.md
Instructions for cosmix/loom, covering claude.md, project overview, build commands, architecture and source layout (loom/src/).
agentic-workflow CLAUDE.md
Instructions for gtrabanco/agentic-workflow, covering claude.md, repository layout, working rules, authoring a skill and hand off, don't compose across a model/effort boundary.
autovault CLAUDE.md
Instructions for autoworks-ai/autovault, covering claude.md, project, common commands, architecture and request flow.
claude-for-strategy CLAUDE.md
Instructions for daddia/claude-for-strategy, covering claude.md, layout, validation — run before opening a pr, 2. json sanity and 3. consulting reference mirrors.
capgo-skills AGENTS.md
AGENTS.md instructions for Cap-go/capgo-skills, covering agents.md, quick start, install dependencies, build the plugin (typescript + rollup + docgen) and full verification (ios, android, web).
agents-config CLAUDE.md
Claude Code instructions for artivilla/agents-config, covering agent config, commands, testing, key files and verification.