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 iampantherr/SecureContext --skill designer-coordination-rulesgit clone --depth 1 https://github.com/iampantherr/SecureContextWrote 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/iampantherr/securecontext/designer-coordination-rules)<a href="https://agentmods.dev/skills/iampantherr/securecontext/designer-coordination-rules"><img src="https://agentmods.dev/badge/skills/iampantherr/securecontext/designer-coordination-rules.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.00020 | $0.00390 |
| Opus 5 | $0.00010 | $0.00195 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
designer-coordination-rules 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 today.
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
COORDINATION RULES
(Extracted from roles.json deepPrompt for the designer role during the v0.19.0 role/skill split. Original content preserved verbatim. Edit freely; the mutator will propose improvements based on skill_runs telemetry once this skill is invoked by an agent.)
- Call
zc_recall_context()first to read project context, brand guidelines, and prior design decisions. - When starting a new surface, use
zc_search(['design system tokens', 'existing components', 'brand guidelines'])before creating anything new. - Produce output as structured design specs (JSON or markdown) that engineers can implement without guessing.
- When a design decision has long-term system implications, use
zc_rememberto persist it. - Broadcast design proposals via
zc_broadcast({type:'PROPOSED', agent_id:'designer', summary:'DESIGN SPEC: ...'})with a link or inline spec. - Call
zc_summarize_session()when a design phase is complete.
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.
- today First seen · 31 lines · 20 tokens per session scan A d322f9de40a6
designer-coordination-rules is a skill published in the GitHub repository iampantherr/SecureContext (8 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 390 once invoked, about $0.0001 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-08.
Other skills, from other repositories
contribution-workflow
Create or document a contribution workflow for a design system — the multi-stage process for evaluating, accepting, and shepherding new contributions through to publication. Trigger when someone says: how should someone contribute, contribution process, adding a new component, contribution guidelines, what's the…
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).