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 skills add jqaisystems/jqai-ai-skills --skill agents-md-writergit clone --depth 1 https://github.com/jqaisystems/jqai-ai-skillsWrote 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/jqaisystems/jqai-ai-skills/agents-md-writer)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/agents-md-writer"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/agents-md-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/agents-md-writer"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/agents-md-writer.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.00798 |
| Opus 5 | $0.00043 | $0.00399 |
| Sonnet 5 | $0.00017 | $0.00160 |
| Haiku 4.5 | $0.00009 | $0.00080 |
Grade A, and why
agents-md-writer 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 12d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md Writer
Claude Code auto-discovers .claude/skills/. Codex and most other agents do not. Without a contract, half your tooling is invisible to half your agents. This skill writes that contract: one AGENTS.md that turns your skill folder into required reading for any agent, plus a CLAUDE.md pointer that keeps a single source of truth.
Step 1: Inventory the workspace
- List
.claude/skills/at the workspace root: every folder with a SKILL.md, and itsnameanddescriptionfrontmatter. - Note which are real folders and which are links into a shared library (both work; the contract references the workspace-relative path either way).
- Read any existing AGENTS.md or CLAUDE.md so you extend rather than clobber. Per-project files deeper in the tree stay untouched.
Step 2: Group the skills
Group by task domain, not alphabetically, so an agent can find the right skill from the task in front of it. Typical groups: Design, Writing, Business, Development, Workflow. Two or three groups beat seven.
Step 3: Write AGENTS.md
Structure, proven in real dual-agent workspaces:
# AGENTS.md
Workspace-level guidance for all projects under <root>. Applies to any agent that reads AGENTS.md.
## Local skills
Skills live in `.claude/skills/`. Claude Code auto-discovers them.
Other agents should treat the files referenced below as required reading,
because they do not auto-load skills from this folder.
## <Group> skills
When a task involves <domain>, read the relevant skill file first and apply its guidance.
- **<skill-name>** (`.claude/skills/<skill-name>/SKILL.md`)
One line: what it covers and when it is required.
How to use them:
- <task shape>: read **<skill-a>** first, then **<skill-b>**.
- These are reference guidance, not code. Read the SKILL.md, then apply.
## <Hard rules>
Any non-negotiable workspace rules an agent must follow in every output.
The per-skill line answers "when is reading this mandatory", not just "what is this".
What ships with it
1 file 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.
- 12d ago First seen · 80 lines · 86 tokens per session scan A 0914f3423874
agents-md-writer is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 798 once invoked, about $0.0004 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
reins
Drive the user's real, logged-in browser from the shell via the reins CLI. Because it's their actual browser, every site is already authenticated — so you can scrape behind logins, read cookies/tokens/localStorage, watch and replay live API traffic, call a site's own API as the signed-in user, and…
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.
review-plan
Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.