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 gosha70/code-copilot-team --skill origin-confirmationgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/gosha70/code-copilot-team/origin-confirmation)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/origin-confirmation"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/origin-confirmation/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/gosha70/code-copilot-team/origin-confirmation"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/origin-confirmation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.02287 |
| Opus 5.5 | $0.00016 | $0.00915 |
| Sonnet 5.5 | $0.00008 | $0.00457 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
origin-confirmation scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- For `urls:`: fetch each URL (`curl -fsSL`, with caching) and read How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Origin-Confirmation Circuit Breaker
Before producing any plan, rubric, evaluation, build, or merge for a feature, you MUST locate and re-read the origin artifact — the user's original description of the idea — and verify that the working spec/plan/PR is a faithful realisation of it.
The latest in-repo spec.md / plan.md is not automatically the
origin. Those are derived artifacts that may already be drifting. The
origin lives in the issue body, external references the user has cited,
and the user's own messages.
This skill is always-on. If a session derives an implementation from a derived spec without re-checking against the origin, that session has violated this skill.
Origin frontmatter convention
Every specs/<feature-id>/plan.md carries an origin: block in YAML
frontmatter. scripts/validate-spec.sh enforces it.
---
feature_id: example-feature
spec_mode: full | lightweight | none
status: draft | approved
origin:
# at least one of: issue, urls, transcripts
issue: gosha70/code-copilot-team#12
urls:
- https://gist.github.com/.../llm-wiki # Karpathy's LLM Wiki gist
- https://www.mindstudio.com/.../wiki # MindStudio explainer
transcripts:
- specs/example-feature/origin/2026-05-04-user-directive.md
origin_claim: |
One paragraph in the user's words: what the user originally asked
for, before any spec/plan derived artifacts. Quote literally where
possible. This is the machine-checkable target for the alignment
check.
---
Escape hatches
Some specs genuinely have no external origin (pure-internal cleanups,
generator refactors, test plumbing). Those use the internal exemption:
origin:
type: internal
reason: "Refactor generator hook ordering — no user-facing behavior change."
A few legacy specs may have an origin that we cannot honestly recover.
Those use the unrecoverable marker, which exits 5 from the verifier
and surfaces the missing origin to anyone who touches the spec next:
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.
- 1mo ago First seen · 242 lines · 41 tokens per session scan A 32cec91103dd
origin-confirmation is a skill published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 41 tokens to every session and 2,287 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
fleet
Fan out a fleet of independent agent-deck child sessions from inside a session and check their progress non-blockingly. Use when the user wants to "launch several/N sessions", "fan out", "run agents in parallel", "spin up a fleet", "kick off background agents", or "check progress from the main session" without…
watcher-creator
Guide for creating agent-deck watchers conversationally. This skill should be used when users want to set up a new watcher (webhook, ntfy, github, slack, gmail) to route events to a conductor. It walks the user through selecting an adapter type, gathering required settings, generating watcher.toml and clients.json…
agent-deck
Helper scripts live in this skill's scripts/ folder. Resolve them from the base directory shown when the skill loaded, not from the user's project.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
x-spec
A system-planning guide that turns a vague idea into a set of linked design documents. It defines goals, modules, interfaces, data, workflows, and ways to check the result.
x-audit-arch
A project-wide architecture review skill that checks whether code is placed in the right modules and whether important definitions have one reliable source.