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 commands/ackeskin/contexture/wrapgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/commands/ackeskin/contexture/wrap)<a href="https://agentmods.dev/commands/ackeskin/contexture/wrap"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/wrap.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.00070 | $0.00385 |
| Opus 5 | $0.00035 | $0.00192 |
| Sonnet 5 | $0.00014 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
wrap 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.
What it actually says
Run the wrap skill.
/wrap sequences the session-closing ceremony in one pass, driving the existing organs (it does not reimplement them):
/wrap— run the full ceremony: coordinate teardown → checkpoint (if a module/corpus change was built) → recap (with §7.4 doorways suppressed — /wrap owns them) → close-out (if a slug shipped) → update-changelog (if a non-slug ship and close-out didn't run) → BACKLOG-shipped-row sweep → build-progress memory offer. Each step is conditional and skipped silently when it doesn't apply.
It reads the autonomy contract once to set the interrupt posture (forks-only runs the reversible spine uninterrupted; every-step confirms each step). The reversible read/draft/detect spine auto-runs; every canonical write (recap file, capture, spec reconcile, artefact move, changelog line, BACKLOG-row removal, build-progress memory edit) passes its own accept/edit/reject gate. When close-out runs, the changelog step is suppressed (close-out contains the changelog write — no double-offer).
The manual /wrap never auto-fires. An optional SessionStart-recovery hook (enabled:false by default) can propose /wrap at the next session start when the prior session shipped work whose terminus was never run.
See ~/.claude/skills/wrap/SKILL.md for the full procedure.
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 · 16 lines · 70 tokens per session scan A 5dd48cb7e569
wrap is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 385 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-09-03.
Other commands, from other repositories
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
test-suite
Run comprehensive test suite with coverage analysis.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
security-scan
Run security audit on codebase.