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 OutlineDriven/odin-codex-plugin --skill edit-articlegit clone --depth 1 https://github.com/OutlineDriven/odin-codex-pluginWrote 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/outlinedriven/odin-codex-plugin/edit-article)<a href="https://agentmods.dev/skills/outlinedriven/odin-codex-plugin/edit-article"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/edit-article/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/outlinedriven/odin-codex-plugin/edit-article"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-codex-plugin/edit-article.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.00061 | $0.00828 |
| Opus 5.5 | $0.00024 | $0.00331 |
| Sonnet 5.5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
edit-article 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- edit-article — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mechanical, structural-only edits to prose. Voice and register are load-bearing and preserved verbatim.
Allowed transformations
- Restructure section order to respect information dependencies (treat info as a DAG; later sections may depend on earlier, never vice versa).
- Split a paragraph carrying two distinct points into two paragraphs.
- Merge two short paragraphs that carry the same point into one.
- Remove redundant sentences, clauses, or words that repeat what was already stated.
- Consolidate parallel lists or tables into a single canonical form when content overlaps.
- Tighten run-on sentences into shorter, clearer ones — preserving the original meaning and the original word choice where possible.
- Cap paragraphs at ~240 characters where doing so requires no rephrasing.
- Promote inline asides into footnotes or sidebars when they break flow.
- Demote redundant headings; promote orphan paragraphs to their own subsection.
Forbidden transformations (hard fence)
- Do NOT change voice (active/passive, first/second/third person).
- Do NOT change register (formal ↔ casual).
- Do NOT change tone (technical, decision-oriented, imperative).
- Do NOT rewrite ODIN-mandated phrasing — terse imperative, third-person, English-mandate, decision-first prose stays.
- Do NOT introduce new claims, examples, or analogies that were not in the source.
- Do NOT remove technical specificity (file paths, command flags, version numbers, named constants).
- Do NOT rename headers, fields, or list items even if they look redundant — those are structural and load-bearing.
- Do NOT translate non-English-mandate content into a different style "for clarity."
- Do NOT add emojis, gradients of warmth, marketing language, or hedging.
If a transformation seems necessary but lives in the forbidden list, STOP and surface the question to the user.
Protocol
- Dispatch Explore agent (or read directly for ≤50 LOC) to map the document into sections by heading. Build the dependency graph.
- Confirm the section order and graph with the user before any edit.
- For each section, in dependency order:
- Identify candidate transformations from the allowed list.
- Apply only those. Surface any forbidden-list candidates as questions.
- Diff with
difftafter the edit; reject the change if voice/register/tone shifted.
- After all sections are processed, re-read the document end-to-end. Confirm flow without re-editing.
- Commit with message:
docs: tighten <document-name> (mechanical edits only).
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.
- 1mo ago First seen · 64 lines · 61 tokens per session scan A 96b8fd3e8fb2
edit-article is a skill published in the GitHub repository OutlineDriven/odin-codex-plugin (14 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 828 once invoked, about $0.0002 per session on Opus 5.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
git-guardrails-claude-code
Install a Claude-Code PreToolUse hook that blocks destructive git commands (push variants including force-push, hard reset, force clean, branch -D, checkout/restore overwrites) before Bash runs them. Use when the user wants git safety rails, force-push prevention, or repository-wipe protection.
duet
Two-party posture — user as director, agent as executor; every fork, tradeoff, or choice surfaced via batched AskUserQuestion with a recommended default. Use when the user invokes /duet, says "ask before" / "pair with me" / "human-in-the-loop", or for aesthetic/architectural/irreversible decisions.
explore
Read-only codebase exploration: discovery, structural reading, and emission of architecture/pattern/tooling/dependency summaries. Use to understand existing code, map files, trace function flow, locate symbols, or build pre-implementation context. Uses a staged 1/3/5 Explore-agent escalation protocol scaled to scope.…
deps-upgrade
Dependency-upgrade campaign — outdated scan, batch-by-severity, breaking-change remediation, lockfile audit. Use when CVEs require remediation, when a major upstream version lands, when stack compatibility forces a sweep, or on a scheduled (quarterly) hygiene cadence. CVE-driven bumps consume security audit findings…
type-driven
Type-driven development. Use when developing with refined types, state machines encoded in types, or proof-carrying types; enforces totality and exhaustive pattern matching.
design-by-contract
Design-by-Contract (DbC) development. Use when implementing with formal preconditions, postconditions, and invariants across any language.