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/aurehub/skills/agents-mdgit clone --depth 1 https://github.com/aurehub/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/aurehub/skills/agents-md)<a href="https://agentmods.dev/instructions/aurehub/skills/agents-md"><img src="https://agentmods.dev/badge/instructions/aurehub/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 | $0.00782 | $0.00782 |
| Opus 5 | $0.00391 | $0.00391 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
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 4d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository stores reusable agent skills. Add new skills under skills/<skill-name>/. Each skill should include SKILL.md; optional files include README.md, SKILL.tests.yaml, references/, and scripts/. Use template/SKILL.md.template as the starting point for new skills. Repository-level automation lives in scripts/, including scripts/publish-clawhub.sh.
Build, Test, and Development Commands
Install the skill collection locally with npx skills add aurehub/skills. Create a new skill from the template with mkdir skills/my-new-skill && cp template/SKILL.md.template skills/my-new-skill/SKILL.md. Run the existing script tests from skills/xaut-trade/scripts/ with npm test. Publish one skill with ./scripts/publish-clawhub.sh skills/<skill-name> <version>. Publish all non-example skills with ./scripts/publish-clawhub.sh --all patch. Add --dry-run before publishing to preview changes.
Coding Style & Naming Conventions
Skill directory names and frontmatter name values must be lowercase and hyphenated, and they should match exactly, for example skills/xaut-trade/ and name: xaut-trade. Keep user-facing content in English. Write concise Markdown instructions with progressive disclosure: core workflow in SKILL.md, detailed material in references/, and executable helpers in scripts/.
Testing Guidelines
Add or update SKILL.tests.yaml when a skill has trigger logic or structured behavior to validate. For script-backed skills, keep tests close to the code, for example skills/xaut-trade/scripts/__tests__/helpers.test.js. Name test files *.test.js for Node helpers. Run targeted tests in the package directory before opening a PR.
Commit & Pull Request Guidelines
Follow the conventional style already used in git history: feat:, chore:, refactor:, i18n:. Keep commit scopes focused on one skill or one repo-level change. Pull requests should explain what changed, list affected skills, mention any new commands or config files, and include sample prompts or terminal output when behavior changes.
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.
- 4d ago First seen · 38 lines · 782 tokens per session scan A 4c3be5f249f0
skills AGENTS.md is an instructions file published in the GitHub repository aurehub/skills (10 stars, last pushed 4mo ago), licensed MIT. It adds 782 tokens to every session, about $0.0039 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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.