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 create-agentsmdgit 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/create-agentsmd)<a href="https://agentmods.dev/skills/boshi-xixixi/traeskill/create-agentsmd"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/create-agentsmd/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/create-agentsmd"><img src="https://agentmods.dev/badge/skills/boshi-xixixi/traeskill/create-agentsmd.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.00016 | $0.01658 |
| Opus 5 | $0.00008 | $0.00829 |
| Sonnet 5 | $0.00003 | $0.00332 |
| Haiku 4.5 | $0.00002 | $0.00166 |
Grade A, and why
create-agentsmd 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-agentsmd — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create high‑quality AGENTS.md file
You are a code agent. Your task is to create a complete, accurate AGENTS.md at the root of this repository that follows the public guidance at https://agents.md/.
AGENTS.md is an open format designed to provide coding agents with the context and instructions they need to work effectively on a project.
What is AGENTS.md?
AGENTS.md is a Markdown file that serves as a "README for agents" - a dedicated, predictable place to provide context and instructions to help AI coding agents work on your project. It complements README.md by containing detailed technical context that coding agents need but might clutter a human-focused README.
Key Principles
- Agent-focused: Contains detailed technical instructions for automated tools
- Complements README.md: Doesn't replace human documentation but adds agent-specific context
- Standardized location: Placed at repository root (or subproject roots for monorepos)
- Open format: Uses standard Markdown with flexible structure
- Ecosystem compatibility: Works across 20+ different AI coding tools and agents
File Structure and Content Guidelines
1. Required Setup
- Create the file as
AGENTS.mdin the repository root - Use standard Markdown formatting
- No required fields - flexible structure based on project needs
2. Essential Sections to Include
Project Overview
- Brief description of what the project does
- Architecture overview if complex
- Key technologies and frameworks used
Setup Commands
- Installation instructions
- Environment setup steps
- Dependency management commands
- Database setup if applicable
Development Workflow
- How to start development server
- Build commands
- Watch/hot-reload setup
- Package manager specifics (npm, pnpm, yarn, etc.)
Testing Instructions
- How to run tests (unit, integration, e2e)
- Test file locations and naming conventions
- Coverage requirements
- Specific test patterns or frameworks used
- How to run subset of tests or focus on specific areas
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.
- 7d ago First seen · 250 lines · 16 tokens per session scan A 97b71d3f7c5e
create-agentsmd is a skill published in the GitHub repository boshi-xixixi/TraeSkill (263 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 1,658 once invoked, about $0.0001 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-09-03.
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.