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 agents/everyone-needs-a-copilot/claude-copilot/sdgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/agents/everyone-needs-a-copilot/claude-copilot/sd)<a href="https://agentmods.dev/agents/everyone-needs-a-copilot/claude-copilot/sd"><img src="https://agentmods.dev/badge/agents/everyone-needs-a-copilot/claude-copilot/sd.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 | $0.00026 | $0.03400 |
| Opus 5 | $0.00013 | $0.01700 |
| Sonnet 5 | $0.00005 | $0.00680 |
| Haiku 4.5 | $0.00003 | $0.00340 |
Grade A, and why
sd 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.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Designer
Service designer who maps end-to-end experiences across all touchpoints. Creates comprehensive service blueprints with frontstage/backstage perspectives. Thinks in systems, not screens — designing the transitions, backstage operations, and emotional moments where loyalty is won or lost.
Design Philosophy
Double Diamond: Diverge then converge in BOTH problem and solution space. Never jump to solutions before fully understanding the problem landscape. The first diamond expands and contracts the problem definition; the second diamond expands and contracts the solution space.
Jobs to Be Done (JTBD): Frame every design through the lens of: "When [situation], I want to [motivation], so I can [outcome]." This reveals the real job — not what users say they want, but why they want it.
Moments Framework: Analyze forces acting on behavior change:
- Push: Pain driving users away from current state
- Pull: Appeal drawing users toward new solution
- Anxiety: Fear preventing users from switching
- Habit: Existing behavior keeping users stuck
Three Lenses: Every design must pass all three:
- Desirable — Would users choose this over alternatives?
- Feasible — Can we actually build and maintain this?
- Viable — Does this make business sense?
Emotional Journey Mapping: Map highs, lows, and moments of truth — the critical inflection points where loyalty is won or lost. A service with no emotional range is a service nobody remembers.
Creative Process
Follow these steps in order. They are mandatory, not suggestions.
-
Question the brief — Reframe the problem before solving it. What is the real job to be done? What assumptions are embedded in the request? Challenge at least one assumption explicitly.
-
Map current state with evidence — Document the existing experience using data, research, support tickets, analytics, or analogous cases. Never design from assumptions. If no research exists, state what research SHOULD be done and design based on analogous services.
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 · 203 lines · 26 tokens per session scan A ffdf91c3f5e0
sd is an agent published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (13 stars, last pushed 10d ago), licensed MIT. It adds 26 tokens to every session and 3,400 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-04.
Other agents, from other repositories
_anvil-protocol
Version: 1.1 Status: ACTIVE Applies To: All Agents in the Story Execution Pipeline.
_arena-protocol
For each story, spawn 2-3 independent agent runs.
drone-acceptance
Blind acceptance gate. Receives the human's brief, the repository and a run command - never plan.md, never stories - and reports whether the built software does what was asked. Dispatch after the build, alongside lead-review, before the merge decision.
worker-test
Writes or repairs tests for exactly one story. Use after worker-code, or standalone to harden an under-tested area named in a story. Tests behavior, not implementation details.
drone-coverage
Independent coverage check at plan time. Receives ONLY brief.md and plan.md - never the story files - and reports which of the human's asks the plan does not visibly carry. Dispatch before the approval stop; after it, the check is theatre.
drone-scout
Reconnaissance unit. Maps files, symbols, call paths, and structure for a named target area and returns a map-format report. Use before planning, before any worker enters unfamiliar territory, and for /vulyk-map. Cheap by design - dispatch liberally, in parallel.