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 KaelinGraf/redraft --skill redraft-initgit clone --depth 1 https://github.com/KaelinGraf/redraftWrote 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/kaelingraf/redraft/redraft-init)<a href="https://agentmods.dev/skills/kaelingraf/redraft/redraft-init"><img src="https://agentmods.dev/badge/skills/kaelingraf/redraft/redraft-init.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.1 | $0.00055 | $0.00626 |
| Opus 5 | $0.00028 | $0.00313 |
| Sonnet 5 | $0.00011 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
redraft-init 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 8d 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
Follow these steps in order. Do not skip ahead or combine steps.
-
Already a graph repo? Check whether
graph/nodes/exists at the project root. If it does, this project already has a redraft graph -- verify.mcp.jsonpoints at it and stop here; do not re-initialize or touch anything. -
Is the engine installed? Run
command -v redraft. If it's missing, print the install steps verbatim for the user to run themselves and stop -- do not install it yourself:git clone https://github.com/KaelinGraf/redraft.git redraft cd redraft uv tool install --from . redraft -
Birth the graph. Run
redraft init <project root>/redraft-graph. If that directory already exists and is non-empty, ask the user first before doing anything -- never overwrite silently. -
Register it at project scope:
claude mcp add --scope project -e REDRAFT_DIR=<abs path to redraft-graph> -e PYTHONPATH= --transport stdio redraft -- redraft serveDo not use
${CLAUDE_PROJECT_DIR}here: this.mcp.jsonis registered from the code project, so CLAUDE_PROJECT_DIR would expand to the code project's root, not the graph directory -- REDRAFT_DIR must be spelled out as an absolute path. -
Gitignore it. Append
redraft-graph/to the project's own.gitignore-- the graph is a separate repo with its own git history (see the engine's README, "Engine and graph are separate repos"); it must never be swept into the code project's commits. -
Tell the user to restart the session. The MCP tools do not appear until Claude Code restarts. Never claim the tools are live before that happens.
-
Report back compactly: where the graph was birthed, that it's registered at project scope, and that a restart is needed.
What NOT to do
- Never use
--scope user-- this graph belongs to this project, not to every project the user opens. - Never point
REDRAFT_DIRat the code project's own root -- it must be the dedicated graph directory from step 3, never the root that holds the project's source. - Never seed or write any nodes during setup. Setup only births an empty graph and registers it; populating it is a separate, later activity driven by the organizing protocol.
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.
- 8d ago First seen · 53 lines · 55 tokens per session scan A 70df3ecab66e
redraft-init is a skill published in the GitHub repository KaelinGraf/redraft (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 626 once invoked, about $0.0003 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 skills, from other repositories
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
understand-figma
Analyze a Figma file via the Figma REST API and generate an interactive design knowledge graph (pages, screens, components, component sets, instances, design tokens) with a kind:"design" dashboard.
kanban-board
A Kanban board is a visual task list with columns for stages such as To do, In progress, In review, and Done. It can show filters, labels, due dates, assignees, comments, and swimlanes that group cards.
acid-blue-business
A visual presentation style for modern business topics, using electric blue with black, white, and grey, directional layouts, and clear spacing. It is intended for business content rather than traditional data dashboards.
product-roadmap
Track milestone progress across four layers of truth — decision state (PDR status), execution state (live issue tracker via MCP), evidence state (code-vs-PDR verification), and gate state (milestone gates). Shows honest completion, done-means warnings, and updates status only when all layers are green. Use for weekly…
workspace
Multi-repo workspace coordinator for shared team context. Initialize .adlc/ structure, configure .gitignore, discover child repos, link them as Git submodules, and audit workspace health. Use --init for first-time setup, default mode for ongoing auditing.