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.
git 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/blueprint)<a href="https://agentmods.dev/commands/ackeskin/contexture/blueprint"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/blueprint/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/commands/ackeskin/contexture/blueprint"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/blueprint.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.00073 | $0.00488 |
| Opus 5.5 | $0.00029 | $0.00195 |
| Sonnet 5.5 | $0.00015 | $0.00098 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
blueprint 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.
What it actually says
Run the blueprint skill.
Forms:
/blueprint <slug>— Mode 1 (intent-driven). Author from.claude/visions/<slug>/,.claude/specs/<slug>/v<M>.md(active), and.claude/plans/<slug>/v<N>.md(active, optional). The "after planning, before coding" path./blueprint <slug> --from-code— Mode 2 (from code). Author from the codebase +.claude/codemap.mdfor a system that was never specced. Inferred runtime flows are labelled "inferred — verify"./blueprint(no slug) — resolve the slug like/draft-plan:defaultif active, else the single active slug, else list and ask. Auto-selects Mode 2 if the resolved slug has no vision/spec.
A blueprint shows what we wanted (intent from vision + spec) and what we're building now (the mature concrete shape: classes, interfaces, dependencies, module relationships, build order) — the commit-point view, not a process narrative. Output is presented for accept / edit / reject before anything is written (the accept/edit/reject review gate). On accept, writes .claude/docs/<slug>/v<N>.md (versioned, spec-pinned) and an Obsidian vault artefact under Projects/<ProjectFolder>/Docs/.
Mermaid only. Manual and optional — /draft-plan offers it at its close but never fires it automatically. Does not merge with /draft-plan (the plan stays the stepped how; the blueprint is the concrete what).
See ~/.claude/skills/blueprint/SKILL.md for the full procedure (both modes, the three-part structure, the output contract) and ~/.claude/skills/blueprint/mermaid-templates.md for the diagram templates.
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 · 18 lines · 73 tokens per session scan A a4265cb645c1
blueprint is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 73 tokens to every session and 488 once invoked, about $0.0003 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-31.
Other commands, from other repositories
migrate
Generate and manage database migrations.
context-stats
Display context window usage and token statistics.
deps-update
Audit and update dependencies safely.
security-scan
Run security audit on codebase.
test-suite
Run comprehensive test suite with coverage analysis.
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.