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/an8079/take-skills/agents-mdgit clone --depth 1 https://github.com/an8079/take-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/instructions/an8079/take-skills/agents-md)<a href="https://agentmods.dev/instructions/an8079/take-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/an8079/take-skills/agents-md.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.00825 | $0.00825 |
| Opus 5 | $0.00413 | $0.00413 |
| Sonnet 5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
take-skills 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 5d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Agent Catalog
Version: v1.0.0 | Updated: 2026-03-01
Multi-agent orchestration system for claude-studio. Each agent has a specialized role in the development lifecycle.
Agent Overview
| Agent | Complexity | Primary Use |
|---|---|---|
interviewer |
Standard | Requirements discovery |
architect |
High | System design |
coder |
Standard | Implementation |
reviewer |
Standard | Code review |
debug-helper |
Standard | Debugging |
Agent Specifications
interviewer
Role: Requirements Discovery
When to use:
- User has a vague idea
- Need to clarify scope
- Hidden assumptions need to be surfaced
- Socratic questioning required
Protocol:
- Ask clarifying questions
- Surface hidden constraints
- Define acceptance criteria
- Document requirements
Example invocation:
/interview "I want to build a task management app"
architect
Role: System Design
When to use:
- New project initialization
- Major feature design
- Technology selection
- Boundary definition
Protocol:
- Analyze requirements
- Design system boundaries
- Define interfaces
- Evaluate tradeoffs
- Document architecture
Example invocation:
/spec "design a REST API for task management"
coder
Role: Implementation
When to use:
- Feature development
- Refactoring
- Test implementation
- Bug fixes
Protocol:
- Review specifications
- Implement feature
- Write tests
- Verify against spec
Example invocation:
/code "implement user authentication"
reviewer
Role: Code Review
When to use:
- Before merging changes
- Quality assurance
- Security review
- Performance review
Protocol:
- Review code changes
- Check for defects
- Verify best practices
- Provide feedback
Example invocation:
/review "review the auth module"
debug-helper
Role: Debugging Assistant
When to use:
- Build errors
- Runtime exceptions
- Logic bugs
- Performance issues
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.
- 5d ago First seen · 211 lines · 825 tokens per session scan A a299e2d254c9
take-skills AGENTS.md is an instructions file published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 825 tokens to every session, about $0.0041 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.