Borrowing it
Nothing to install: this file belongs to okqixiaobao727-design/agentcrew-dev-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/okqixiaobao727-design/agentcrew-dev-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/okqixiaobao727-design/agentcrew-dev-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/okqixiaobao727-design/agentcrew-dev-skills/agents-md)<a href="https://agentmods.dev/instructions/okqixiaobao727-design/agentcrew-dev-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/okqixiaobao727-design/agentcrew-dev-skills/agents-md/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/instructions/okqixiaobao727-design/agentcrew-dev-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/okqixiaobao727-design/agentcrew-dev-skills/agents-md.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.00368 | $0.00368 |
| Opus 5 | $0.00184 | $0.00184 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
agentcrew-dev-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 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.
What it actually says
AGENTS.md
Validating your work
scripts/test.py is the only test command; a name it doesn't know prints the list of suites.
While you work — the suite that tests what you changed, plus the validator:
python3 scripts/test.py --asset driver
python3 scripts/validate_plugin_tree.py
A file inside skills/*/assets/<asset>/ is tested by that asset's suite. Everything else is
tested by root: scripts/, config/, hooks, and the spine — the files under
skills/crew/assets/ that sit outside any asset (accounts.py, advance.py, machine_log.py,
merge_driver.py, codex/).
Before you hand the work back — the full gate, if you touched the spine:
python3 scripts/test.py # every suite; give it a fifteen-minute timeout
Six of the seven suites import the spine, so a focused run cannot see what a spine change broke.
A change contained to one asset needs no local full gate when its commit is pushed before another
run is cut: CI runs the full gate on every push and pull request to main. For an unpushed base,
this repo's [preflight] gate runs that same full gate in the fresh Crew worktree at the selected
local base tip, before the Driver launches the Run.
Run the validator every time — it costs a second, and its residue lint reads your gitignored
.agentcrew-local-identifiers, which CI has no copy of.
Report what you ran, verbatim, beside the result. A skipped gate reported as a pass is worse than a red one (ADR-0016).
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 · 36 lines · 368 tokens per session scan A b2f342501851
agentcrew-dev-skills AGENTS.md is an instructions file published in the GitHub repository okqixiaobao727-design/agentcrew-dev-skills (1 stars, last pushed 4d ago), licensed MIT. It adds 368 tokens to every session, about $0.0018 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
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.
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 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).
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).