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 tagit 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/ta)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/ta"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/ta/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/ta"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/ta.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.00044 | $0.01821 |
| Opus 5.5 | $0.00018 | $0.00728 |
| Sonnet 5.5 | $0.00009 | $0.00364 |
| Haiku 4.5 | $0.00004 | $0.00182 |
Grade A, and why
ta 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Architect
Use this skill before non-trivial implementation.
Operating Lens
- Understand the existing system before proposing changes.
- Prefer the simplest viable design that matches local patterns.
- Make tradeoffs explicit.
- Design for failure modes and maintainability.
- Use
tcfor substantial PRDs, tasks, and architecture work products. - Verify installed third-party API surfaces with Live Docs before planning around them.
Success Criteria
- Existing architecture and constraints are understood before recommendations.
- Tradeoffs and rejected alternatives are documented.
- Implementation tasks include explicit test requirements.
- Security, operations, data, and failure modes are called out when relevant.
- Substantial plans are stored in
tc, not loose markdown. - Third-party API assumptions are checked with
cc docswhen available.
Taste Applicability
Read only taste rules whose lens includes this specialist and whose Applies: scope matches this project or is personal; do not import another project's rule. Project constraints and repository instructions outrank personal taste. State which rule was set aside on conflict.
Workflow
-
Read
08-taste/INDEX.mdfrom the nearestpaths.knowledge_repoentry that has one — resolved tensions from this owner's own feedback, personal tier only, empty until earned. Apply the reasoning, not the example; when a rule does not fit, say so rather than forcing it. -
Check task context with
tc task get <taskId> --jsonwhen a task exists. -
Hydrate config with
eval "$($HOME/.local/bin/cc env)"whenccis available. -
Search memory for prior architecture decisions.
-
Read the request, relevant project docs, decision instruments, and surrounding code.
-
Run
cc docs get <pkg> --topic <area> --jsonbefore planning against installed third-party APIs. -
Define scope, non-goals, constraints, and risks.
-
Compare viable approaches and choose one.
-
Break work into concrete implementation and verification units with test expectations.
-
Store architecture decisions and task plans as
tcwork products. -
Route to
$mefor implementation and$qafor verification.
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 ee14d481a088
- 7d ago Changed · +16 lines 4942d482f6cb
- 1mo ago Changed · +59 lines 04b54c9248dc
- 1mo ago First seen · 77 lines · 44 tokens per session scan A a7b228ce3273
ta is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 1,821 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
theokit-agents
TheoKit agent/LLM integration — agents/.ts convention (AgentBuilder), the tool() builder, capabilities (advanced/DI), useAgent client hook.
theokit-ui
@theokit/ui AI-native component library — AI-agent surfaces (ChatThread, ChatMessage, ChatComposer, ToolCallCard, AgentStream), theming, providers; generic primitives (CodeBlock, Sidebar, Button) come from @usetheo/ui.
theokit-gateways
Receiving messages from Telegram, WhatsApp, Slack and other platforms — handleChannelWebhook, the @theokit/gateway- adapters, signature validation, the onMessage seam.
theokit-frontend
TheoKit frontend — file-based routing, layouts, theoFetch typed client, useAgent, React patterns.
theokit-routes
TheoKit server routes — the route() builder, Zod validation, HTTP methods, dynamic params, error handling.
theokit-config
TheoKit configuration — the config() builder, plugins, security, storage, agents, build targets.