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/wukongai/skill-engineering/agents-mdgit clone --depth 1 https://github.com/wukongai/skill-engineeringWhat 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.00422 | $0.00422 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
skill-engineering 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 2d 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Engineering
Skill Engineering is the standalone source of truth for Agent Skill creation, Doctor, behavior evaluation, continuous maintenance, self-evolution, and release safety.
Rules
- Use Simplified Chinese for user-facing collaboration unless the user requests otherwise.
- Feature work requires a spec and plan before implementation.
- Preview before write; apply must reference the same immutable plan.
- Never store credentials, raw sensitive prompts, or full conversations in local state.
- Static Doctor scores are structural readiness, not downstream utility.
- Candidate generation must not receive holdout assertions or baseline scores.
- Canary/Active release requires explicit approval; Global release is out of scope.
- Run pytest, Ruff, Skill validation, credential lint, and diff check before declaring completion.
Self-hosted product workflow
- For a new capability request, self-check existing Skills/scripts/plugins/docs and complete discovery before choosing an artifact. Do not create product/version scaffolding before deciding that a Skill is needed.
- When resuming this existing repository, start with
docs/PRODUCT.md,docs/constitution.md,docs/architecture.md,docs/TASK.md, and the current Sprint. - Feature work requires a current file under
docs/specs/anddocs/plans/before implementation. - Cross-version architecture decisions require an ADR under
docs/adr/. - New ideas that are not part of the active Sprint go to
docs/BACKLOG.md; do not silently expand the current version. - Record daily facts and blockers under
docs/logs/daily/; promote stable rules into formal docs instead of citing the log forever. - Update README, Changelog, Roadmap, Task, Sprint, version sources, tests, and release evidence together before a release claim.
- Use an isolated candidate and the maintenance engine for changes to Skill Engineering; do not edit maintained Skill source as an experiment.
- Commit and push are separate approval points. Never auto-publish, auto-tag, or auto-enable Global scope.
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.
- 2d ago First seen · 27 lines · 422 tokens per session scan A 2322e5bd5aec
skill-engineering AGENTS.md is an instructions file published in the GitHub repository wukongai/skill-engineering (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 422 tokens to every session, about $0.0021 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 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.