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/coordinate)<a href="https://agentmods.dev/commands/ackeskin/contexture/coordinate"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/coordinate/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/coordinate"><img src="https://agentmods.dev/badge/commands/ackeskin/contexture/coordinate.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.00062 | $0.00343 |
| Opus 5.5 | $0.00025 | $0.00137 |
| Sonnet 5.5 | $0.00012 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
coordinate 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 coordinate skill.
Forms:
/coordinateor/coordinate register— register/update this session on the board (what slug + files it owns, status), with a collision check against the others./coordinate check— read the board: what others own, any hand-offs/assignments for this session, any collisions or stale orphan rows./coordinate handoff <session> <note>— leave a note for another session ("ui: I changed the token contract — re-read before wiring")./coordinate coordinator— claim (or release) the coordinator role, which can write assignments other sessions pick up on their next check./coordinate done— tear down this session's row on close.
The shared memory that peer sessions coordinate through when you fragment work across multiple live windows (a /execute per work-stream). It is not /orchestrate (which dispatches subagents within one session). No daemon, no polling — read at start + key moments, write on change. The board is gitignored ephemeral state, carries no secrets, and the coordinator can direct but not force peers. Collisions are surfaced, never auto-resolved; nothing auto-fires.
See ~/.claude/skills/coordinate/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.
- 1mo ago First seen · 18 lines · 62 tokens per session scan A f97779cb01ad
coordinate is a command published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 343 once invoked, about $0.0002 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
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
handoff
Write a session handoff document for continuity.
update-docs
Scan recently modified files and update the matching documentation.
apply
name: OpenSpec: Apply description: Implement an approved OpenSpec change and keep tasks in sync. category: OpenSpec tags: [openspec, apply].
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.