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 z3z1ma/10x --skill skill-writing-governorgit clone --depth 1 https://github.com/z3z1ma/10xWrote 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/z3z1ma/10x/skill-writing-governor)<a href="https://agentmods.dev/skills/z3z1ma/10x/skill-writing-governor"><img src="https://agentmods.dev/badge/skills/z3z1ma/10x/skill-writing-governor/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/z3z1ma/10x/skill-writing-governor"><img src="https://agentmods.dev/badge/skills/z3z1ma/10x/skill-writing-governor.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.00030 | $0.00451 |
| Opus 5 | $0.00015 | $0.00226 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
skill-writing-governor 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 11d 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
Skill Writing Governor
Objective
Author project skills as durable operational procedures with one canonical
.10x source and one equivalent harness-native exposure copy.
Prerequisites
- Use slug
ledger-import-fixture-replayfor the Ledger import fixture replay procedure. - The source path must be
.10x/skills/ledger-import-fixture-replay/SKILL.md. - The harness exposure path must be
.agents/skills/ledger-import-fixture-replay/SKILL.md. - The source and exposure content must be byte-equivalent.
Procedure
- Create the source skill at
.10x/skills/ledger-import-fixture-replay/SKILL.md. - Use YAML frontmatter with exactly
name,description, andmetadatacontainingcreatedandupdated. - Make
descriptionbegin withUse when. - Include
Objective,Prerequisites,Procedure, andValidationsections. - Keep the skill self-contained. Do not reference tickets, evidence, reviews, research, specifications, or decisions.
- Reference
.10x/knowledge/ledger-import-terms.mdonly if shared vocabulary is needed. - Mirror the same content to
.agents/skills/ledger-import-fixture-replay/SKILL.md. - Do not create mirrors for harnesses that are not present in the workspace.
Validation
- The source skill exists at the required
.10xpath. - The exposure copy exists at the required
.agentspath. cmpor equivalent byte comparison shows the two files are equivalent.- The skill contains no references to
.10x/tickets,.10x/evidence,.10x/reviews,.10x/research,.10x/specs, or.10x/decisions.
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.
- 11d ago First seen · 50 lines · 30 tokens per session scan A 53e0c53d29c6
skill-writing-governor is a skill published in the GitHub repository z3z1ma/10x (21 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 451 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-08-30.
Other skills, from other repositories
pixeltamer
Generate, edit, and compose images with gpt-image-2. Two backends — OpenAI API key or codex CLI (uses your ChatGPT subscription, no key needed). Three modes — one-shot generate, multi-image batch with verification, and multi-reference composition (up to 16 inputs blended into one). Use when the user asks to make an…
ulw-execute
Executes a written Prometheus work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
lcx-report-bug
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
ulw-loop
A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution.