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 spec-workflowgit 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/spec-workflow)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/spec-workflow"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/spec-workflow/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/spec-workflow"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/spec-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 71 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00029 | $0.01113 |
| Opus 5.5 | $0.00012 | $0.00445 |
| Sonnet 5.5 | $0.00006 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
spec-workflow 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 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.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Workflow — SDD Specification Protocol
Rules governing when a Software Design Document (SDD) spec is required, what sections it must contain, and how it gates the transition from Plan to Build.
Risk-Based spec_mode Classification
Every planned feature is assigned a spec_mode based on change risk. The Plan agent determines this value and records it in specs/<feature-id>/plan.md YAML frontmatter.
| spec_mode | When to use |
|---|---|
full |
Security changes, schema changes, integration work, features touching more than 2 files |
lightweight |
Features touching 1–2 files, non-critical changes |
none |
Bug fixes (non-security), docs-only changes, trivial or cosmetic changes |
When in doubt, escalate to the next higher mode. Under-speccing a risky change costs more than over-speccing a safe one.
Required Spec Sections per Mode
full
All sections from spec-template.md are required, plus a tasks.md task breakdown:
- User Scenarios
- Requirements
- Constraints / What NOT to Build
- Key Entities
- Success Criteria
tasks.md— discrete, bounded build tasks derived from the spec
lightweight
Only two sections are required in spec.md:
- Requirements
- Constraints
none
No spec.md is required. The Plan agent writes only plan.md.
Plan Approval Gate Protocol
What the Plan Agent Writes
The Plan agent always writes specs/<feature-id>/plan.md regardless of spec_mode. The file must include YAML frontmatter with at minimum:
---
feature_id: <feature-id>
spec_mode: full | lightweight | none
status: draft | approved
origin:
# at least one of: issue, urls, transcripts — OR the explicit
# internal/unrecoverable exemption. See origin-confirmation skill.
issue: <repo>#<number>
urls:
- <external-reference-url>
transcripts:
- specs/<feature-id>/origin/<date>-<slug>.md
origin_claim: |
One paragraph in the user's words quoting their original ask.
---
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 · 120 lines · 29 tokens per session scan A 089ece87f003
spec-workflow is a skill published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 29 tokens to every session and 1,113 once invoked, about $0.0001 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-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.