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/mag123c/toktrack/wrapnpx skills add mag123c/toktrack --skill wrapgit clone --depth 1 https://github.com/mag123c/toktrackWrote 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/mag123c/toktrack/wrap)<a href="https://agentmods.dev/skills/mag123c/toktrack/wrap"><img src="https://agentmods.dev/badge/skills/mag123c/toktrack/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.1 | $0.00009 | $0.00425 |
| Opus 5 | $0.00005 | $0.00212 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 5d 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
Wrap
Flow
Git Status → Doc Check → User Selection → Execute → Complete
Execution
-
Git Status
git status --short git diff --stat HEAD~3 -
Doc Check Checklist (MUST)
Change Target Required trait/type architecture.md on structural change convention conventions.md on new pattern Decisions .dev/DECISIONS.md on new feature/design DECISIONS.md entries (required check):
- New feature implemented → record decision rationale, alternatives, reasons
- Divergence between PLAN and actual implementation → add
**Implementation Note** - New pattern/convention → also update conventions.md
-
Plan Reconciliation (MUST)
Reconcile the PLAN's provenance tags/gates (
[unverified-gate]/[agent-inferred]/Phase 0) one-by-one — close (confirmed/falsified/changed) or explicitly delegate (delegated). No silent TODOs. Unsettled gates = wrap incomplete.Detailed procedure·delegated block·escalation criteria (WRAP=detail/DECISIONS=why/CLAUDE.md=critical·recurring) →
references/reconciliation.md -
User Selection: AskUserQuestion
-
Execute: Run selected items
DSL Rules (ai-context)
- Table > prose
- Codeblock > description
- Core only, minimize lines
Commit
{type}({scope}): {summary}
Completion
wrap complete = skill chain finished
Next task starts with new /clarify or /next
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.
- 5d ago First seen · 57 lines · 9 tokens per session scan A 98934ea135e9
wrap is a skill published in the GitHub repository mag123c/toktrack (188 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 425 once invoked, about $0.0000 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
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, testing, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, testing strategy, and communication standards.
archive
Phase 10.5 — move the slug's workflow artifacts (intake, scout, research, spec, approvals, swarm state, security reports, rendered diagrams) to docs/archive/ / /. Runs before /commit so the committed tree is clean of work-in-flight files. workflow.json stays live and gets archived as the first step of /commit.
commit
Workflow Phase 11 — Commit Preparation and Execution. Stages and commits the work. Requires /grant-commit first (Git Commit Guard enforces a 15-min ad-hoc consent window; inside a workflow the grant is slug-scoped and one grant covers the whole landing).
commit-planner
Split a dirty working tree into single-concern Conventional Commits. The deterministic inventory.mjs helper groups dirty paths by concern (docs, source + paired test, config, governance); main context refines the grouping and presents a commit plan. Read-only until the user approves the plan — it never stages, never…
git-workflow
Skill "git-workflow" from halflength-ampleness75/claude-code-recipes, covering git workflow, branch naming, rules, conventional commits and format.
capture
Harmonia capture stage - record learnings into the right memory tier, then ship structured commits. Use ONLY when explicitly invoked as /harmonia:capture.