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 rules/danielvm-git/bigpowers/craft-skillgit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/craft-skill)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/craft-skill"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/craft-skill.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.00036 | $0.01900 |
| Opus 5 | $0.00018 | $0.00950 |
| Sonnet 5 | $0.00007 | $0.00380 |
| Haiku 4.5 | $0.00004 | $0.00190 |
Grade A, and why
craft-skill 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 today.
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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Skill
HARD GATE — Do NOT name a skill without a two-word verb-noun pair. Do NOT merge a new skill without running
sync-skills.sh. Generated.cursor/rules/and.gemini/artifacts MUST match the source SKILL.md.
CSO Description Discipline (e45s02)
The YAML description is the Catalog Selection Object — the only field agents see when picking a skill.
| Rule | Limit |
|---|---|
| Max length | 1024 characters |
| Voice | Third person |
| Content | Capability + Use when … triggers only |
| Forbidden | Workflow steps, phase chains, numbered lists, → verify:, HARD GATE prose |
Move process detail into the SKILL.md body or REFERENCE.md — never into description.
Agentic STE body discipline (e79s02)
Skill-body instructional prose MUST follow AGENTIC-STE.md.
| Rule | Limit |
|---|---|
| Sentence length | ≤20 words per instruction sentence |
| Voice | Imperative, active |
| Directive terms | MUST, MUST NOT, NEVER, ALWAYS, DO, DO NOT |
| Banned modals | should, might, could, may, consider, try, generally, typically |
| Scope | SKILL.md body only — not YAML description, not terse-mode output |
HARD GATE — Do NOT merge a new or edited skill until
bash scripts/validate-agentic-ste.sh --strict skills/<name>/SKILL.mdexits 0. Fix violations beforesync-skills.sh.
Process
-
Gather requirements — ask user about:
- What task/domain does the skill cover?
- Which use cases must the skill handle?
- Does it need executable scripts or just instructions?
- Any reference materials to include?
- What specs/ output does it produce (if any)?
-
Verify Principles — Ensure the skill aligns with PRINCIPLES.md:
- Is it atomic (verb-noun)?
- Is it "deep" (simple interface, complex internal logic)?
- Does it include Hard Gates?
- Is it verifiable with a
.featurefile?
-
Draft the skill — create:
- SKILL.md with concise instructions (see REFERENCE.md for template)
- Additional reference files if content exceeds 100 lines
- Utility scripts if deterministic operations needed
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.
- today First seen · 196 lines · 36 tokens per session scan A 56f328ab0480
craft-skill is a cursor rule published in the GitHub repository danielvm-git/bigpowers (162 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,900 once invoked, about $0.0002 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.
nextjs
ContextOS rules for nextjs.