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 Everyone-Needs-A-Copilot/claude-copilot --skill megit 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/skills/everyone-needs-a-copilot/claude-copilot/me)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/me"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/me/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/skills/everyone-needs-a-copilot/claude-copilot/me"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/me.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.00039 | $0.01581 |
| Opus 5.5 | $0.00016 | $0.00632 |
| Sonnet 5.5 | $0.00008 | $0.00316 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
me 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineer
Use this skill to make focused, working code changes.
Operating Lens
- Read before editing.
- Follow existing code style, helpers, and module boundaries.
- Fix root causes instead of symptoms.
- Add tests in proportion to risk and blast radius.
- Keep unrelated refactors out of the change.
- Use Live Docs before coding against installed third-party package APIs.
- Treat
$qaas required for implementation work that needs verification. - Follow the fixed acceptance scope and Proportional Verification; a new requirement needs an explicit scope decision, not an automatic extra improvement.
Success Criteria
- Code compiles or the relevant build check passes.
- Focused tests or checks run for the changed behavior.
- New or changed behavior has proportional test coverage.
- Edge cases and errors are handled.
- Implementation details are stored as a
tcwork product when task context exists. - QA-required tasks carry
metadata.requiresQa=trueand are routed to$qa.
Workflow
- Confirm the task, plan, or bug is framed clearly enough to implement.
- Check task context with
tc task get <taskId> --jsonwhen available. - Hydrate config and search memory when
ccis configured. - Inspect the relevant files, current tests, and local patterns.
- Run
cc docs get <pkg> --topic <area> --jsonbefore using third-party APIs. - Make the smallest coherent change.
- Run focused validation first, then broader checks when warranted.
- Store implementation details as a
codework product. - Route to
$qa; do not treat implementation as the final gate.
Iteration Loop
Read ../specialist-agents/references/verification-policy.md once per task before
selecting checks. Apply its behavior/consumer lanes, first-divergent-state diagnosis,
two-hypothesis checkpoint and execution caps. Add tests for missing behavior coverage,
not each edited file; preserve current source-bound QA and report remaining risk.
Methodology
Kent Beck's simple design priority: passes tests, reveals intention, removes duplication, then minimizes elements.
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.
- 6d ago Changed 0d61fe0148e0
- 7d ago Changed · +8 lines b60a7ba9ecff
- 1mo ago Changed · +3 lines 2e0592b2c58a
- 1mo ago Changed · +55 lines 0ef7ca6f6d7f
- 1mo ago First seen · 70 lines · 39 tokens per session scan A b238a75165be
me is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,581 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-09-04.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
module-regression
Govern cross-module regression in large repositories with a REGRESSION.md ledger that records each module's downstream consumers and executable acceptance command. After a change, run the changed module and every affected downstream command, and use observed exit codes as regression evidence under the project's…
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-flakiness
Find flaky tests from CI logs — aggregates pass rates, spots intermittent failures, recommends quarantine. After multiple runs.
maintain-formal-verification-skill
Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for…
prevent-recurrence
Use when correcting an issue or failure reveals a reusable prevention lesson, including code, setup, measurement, validation, workflow, agent mistakes, or accepted code-review findings; when someone says "this keeps happening" or asks how to stop it; or in post-incident follow-up. Fixes the instance (failing-first…