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 skills add AcKeskin/contexture --skill coordinategit 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/skills/ackeskin/contexture/coordinate)<a href="https://agentmods.dev/skills/ackeskin/contexture/coordinate"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/coordinate.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.00090 | $0.03975 |
| Opus 5 | $0.00045 | $0.01988 |
| Sonnet 5 | $0.00018 | $0.00795 |
| Haiku 4.5 | $0.00009 | $0.00398 |
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
coordinate
Multi-session coordination. The pipeline tells you to fragment — /spec and /draft-plan recommend a fresh session per phase — so when you plan several things and spin up multiple live sessions (a /execute window per work-stream), they drift: session A doesn't know what B decided. coordinate is the shared memory those live, peer sessions coordinate through.
It is not orchestrate (which dispatches fire-and-forget subagents within one session and reconverges them). These are independent, user-driven peer sessions with no parent — so coordination is a passive shared board, read-at-action and written-on-change, no daemon or polling. (Folding this into orchestrate's deferred background-session runtime is a later increment.)
The board
<project-root>/.claude/sessions-active.md — gitignored, ephemeral live state (add .claude/sessions-active.md to .gitignore if .claude/ isn't already ignored). One row per active session:
# Active sessions
<!-- coordinator: <label or "none"> -->
| Session | Owns | Status | Updated | Hand-offs / assignments |
|---------|------|--------|---------|-------------------------|
| auth | slug:auth-rework, src/auth/* | executing step 3 | 2026-06-11T14:20 | — |
| ui | slug:settings-ui, src/ui/settings/* | drafting plan | 2026-06-11T14:05 | from auth: "changed the token contract — re-read before wiring" |
Session is a short stable label (the slug it's working on, or a user-given name like auth/ui). The board carries no secrets — paths + labels only.
Hidden identity block (write-authority + liveness). Below the visible table, a hidden HTML-comment block maps each label to the session that owns it:
<!-- identities
auth = { session: e3bd7da4-..., host: DESKTOP-X }
ui = { session: 1a2b3c4d-..., host: DESKTOP-X }
-->
Two mechanisms read this block, both detailed below: a write-authority check (a row-mutating write must come from the session whose identity is recorded, else it is rejected-and-recorded — see Update) and a liveness check (a row is live only while its owning session's transcript is still being written — see Check). The block stays hidden so the visible table is unchanged; it still carries no secrets — a session_id is already on disk as a transcript filename, and host is a machine name. The transcript path is derived, not stored: ~/.claude/projects/<canonical-cwd-slug>/<session_id>.jsonl.
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.
- 3d ago First seen · 135 lines · 90 tokens per session scan A 9cd099e35095
coordinate is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 3,975 once invoked, about $0.0005 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 skills, from other repositories
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
agent-teams
Team composition knowledge for Claude Code Agent Teams - when to suggest teams, optimal sizing, spawn prompt patterns.
ship-roadmap
Found or continue a roadmap autopilot one stage per invocation. Default: human merge. --fullauto is invocation-scoped and uses the transient wrapper only after a fresh audit. Triggers: "ship-roadmap", "ship the roadmap", "autopilot this project".