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 boshi-xixixi/TraeSkill --skill acreadiness-generate-instructionsgit clone --depth 1 https://github.com/boshi-xixixi/TraeSkillWrote 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/boshi-xixixi/traeskill/acreadiness-generate-instructions)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/acreadiness-generate-instructions"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/acreadiness-generate-instructions/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/boshi-xixixi/traeskill/acreadiness-generate-instructions"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/acreadiness-generate-instructions.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.00077 | $0.02132 |
| Opus 5 | $0.00039 | $0.01066 |
| Sonnet 5 | $0.00015 | $0.00426 |
| Haiku 4.5 | $0.00008 | $0.00213 |
Grade A, and why
acreadiness-generate-instructions 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 10d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/acreadiness-generate-instructions — write AI agent instructions
Use this skill whenever the user wants to create, regenerate, or refresh their custom instructions for AI coding agents (Copilot, Claude, etc.). This is the Generate step in AgentRC's Measure → Generate → Maintain loop and the single highest-leverage action for the AI Tooling pillar.
Output options
VS Code recognises several instruction file types — AgentRC generates the most common ones:
| File | Scope | When to use |
|---|---|---|
.github/copilot-instructions.md |
Always-on, whole workspace | Default — VS Code Copilot's native instruction file |
AGENTS.md |
Always-on, whole workspace | Multi-agent repos (Copilot + Claude + others) |
.github/instructions/*.instructions.md |
Scoped by applyTo glob |
Per-area / per-language rules in monorepos |
CLAUDE.md |
Claude-specific | Add via --claude-md (nested only) |
Strategies
flat(default) — single.github/copilot-instructions.mdat the chosen path. Simple, easy to review.nested— hub at.github/copilot-instructions.md+ per-topic detail files at.github/instructions/<topic>.instructions.md, each with anapplyToglob so VS Code only loads the topic when it's relevant. Better for large or multi-stack repos.
Why
.github/instructions/and not.agents/? AgentRC's default nested layout writes to.agents/, which is the right home for agent-agnostic repos (Copilot + Claude + Cursor readingAGENTS.md). For VS Code Copilot specifically, the native location is.github/instructions/withapplyTofrontmatter — that's what Copilot auto-discovers. This skill rewrites AgentRC's nested output to the VS Code-native location whenever the main output is.github/copilot-instructions.md. If you instead chose--output AGENTS.md, nested keeps AgentRC's default.agents/layout.
For monorepos, generate area-scoped instructions with --areas, --area <name>, or --areas-only. Areas are defined in agentrc.config.json. Per-area output is written as VS Code .instructions.md files with an applyTo glob (see below).
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.
- 10d ago First seen · 108 lines · 77 tokens per session scan A b0f4f82099fb
acreadiness-generate-instructions is a skill published in the GitHub repository boshi-xixixi/TraeSkill (262 stars, last pushed 4mo ago), licensed MIT. It adds 77 tokens to every session and 2,132 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-30.
Other skills, from other repositories
<skill-name>
A template for defining a coding-agent skill, including its title, trigger situations, overview, workflow, common mistakes, and optional references.
spec-writing
A method for writing a software specification: a document that records decisions, reasons, boundaries, and ways to judge whether implementation succeeded. It first checks whether important unknowns require user clarification or technical research.
onboarding-unknown-codebase
A method for quickly understanding an unfamiliar codebase, meaning a software project whose structure and behavior you do not yet know. It builds a project map by examining overview files, directories, and one main execution path.
commit-message
A guide for writing clear, traceable Git commit messages using the Conventional Commits format, which labels changes such as features, bug fixes, documentation, and refactoring.
clarifying-questions
Guidance for clarifying vague or assumption-heavy requests before making changes.
debugging
A systematic method for finding the underlying cause of a software bug by observing the failure, forming a hypothesis, and testing it.