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 skills/voxtechnologies/transmute-framework/docsnpx skills add VoxTechnologies/transmute-framework --skill docsgit clone --depth 1 https://github.com/VoxTechnologies/transmute-frameworkWhat 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.00087 | $0.03614 |
| Opus 5 | $0.00044 | $0.01807 |
| Sonnet 5 | $0.00017 | $0.00723 |
| Haiku 4.5 | $0.00009 | $0.00361 |
Grade A, and why
docs 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 yesterday.
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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Generation — Stage 6D
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/docs-detailed-guide.md for the complete documentation procedures, teammate spawn prompts, writing style guidelines, and report templates.
Lead a multi-agent documentation generation project. Generate comprehensive documentation for the complete product: user-facing help docs, API/backend reference, and a developer onboarding guide, all derived from the codebase, PRD, and BRD.
Stage Sequence (recommended ordering): Stage 5B → 6A/6B/6C (parallel) → 6E (Code Refactoring) → 6F (Seed Data) → 6G (Resilience Hardening) → 6D (this stage) → 6H (Pre-Launch) → 6V → 6R → 6P/6P-R → 7 (Deploy)
Prerequisite Checks
Before any documentation work, verify:
- Check that
./plancasting/_audits/implementation-completeness/report.mdexists and shows PASS or CONDITIONAL PASS. If missing, WARN: 'Stage 5B report not found — implementation completeness is unverified. Assuming all features are implemented and proceeding.' If FAIL, STOP: "Stage 5B FAIL — resolve implementation gaps before generating documentation." - If CONDITIONAL PASS, read documented Category C issues. Document those features as "Planned" rather than "Available".
- Check if
./plancasting/_audits/refactoring/report.mdexists (Stage 6E). If missing, WARN: "Stage 6E has not completed. If 6E restructures modules after 6D, documentation structure may need regeneration." Proceed with caution. - Check if
./plancasting/_audits/resilience/report.mdexists (Stage 6G). If missing, note that documentation may need updating after 6G completes. - Check if
./seed/README.mdexists (Stage 6F). If missing, WARN: "Stage 6F has not completed — seed data documentation will be omitted from developer setup guide." - Read
./CLAUDE.mdand./plancasting/tech-stack.mdfor project conventions.
Stage 6D produces internal developer documentation (API reference, architecture, dev guide). Stage 7D produces the external user-facing Mintlify site. Stage 6D always runs; Stage 7D is optional per plancasting/tech-stack.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 219 lines · 87 tokens per session scan A 4518bb8a38eb
docs is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 3,614 once invoked, about $0.0004 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
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
peer-review
Structured manuscript/grant review with checklist-based evaluation. Use when writing formal peer reviews with specific criteria methodology assessment, statistical validity, reporting standards compliance (CONSORT/STROBE), and constructive feedback. Best for actual review writing, manuscript revision. For evaluating…
scientific-critical-thinking
Evaluate scientific claims and evidence quality. Use for assessing experimental design validity, identifying biases and confounders, applying evidence grading frameworks (GRADE, Cochrane Risk of Bias), or teaching critical analysis. Best for understanding evidence quality, identifying flaws. For formal peer review…
statistical-analysis
Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting. Use whenever a user wants to compare groups, test a hypothesis, analyze experimental or survey data, check statistical assumptions, compute required…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…