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 andrewvaughan/agent-council --skill build-featuregit clone --depth 1 https://github.com/andrewvaughan/agent-councilWrote 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/andrewvaughan/agent-council/build-feature)<a href="https://agentmods.dev/skills/andrewvaughan/agent-council/build-feature"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/build-feature/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/andrewvaughan/agent-council/build-feature"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/build-feature.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.00052 | $0.03904 |
| Opus 5 | $0.00026 | $0.01952 |
| Sonnet 5 | $0.00010 | $0.00781 |
| Haiku 4.5 | $0.00005 | $0.00390 |
Grade A, and why
build-feature 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 10d 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 — 443 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full-Stack Feature Implementation Workflow
Execute a full-stack feature implementation across database, backend, frontend, and testing layers. This skill follows the implementation plan produced by /plan-feature and builds all layers with integrated testing.
[!CAUTION] Scope boundary: This skill implements code and commits it. It does NOT create pull requests, push to remote, run code reviews, or submit anything for merge. When implementation and commits are complete, stop and suggest the user run
/review-codenext. Do not proceed to PR creation — that is/submit-pr's job.
Step 1: Load Implementation Plan
Check for an implementation plan using the following priority:
[!NOTE] GitHub issues created by
/plan-featureare task-oriented work items — the decision record remains the authoritative source of council evaluations, rationale, and architectural context. When loading from an issue, always read the referenced decision record for full context.
Option A: GitHub Issue (Primary)
If the user provides a GitHub issue number (e.g., /build-feature 42 or /build-feature #42):
-
Fetch the issue details:
gh issue view <number> --json title,body,labels,state,number -
Validate the issue:
- Confirm it has the
build-readylabel (warn if not — it may not have been through/plan-featureor may need further planning) - If the issue is closed, warn the user and ask whether to proceed
- Confirm it has the
-
Parse the issue body to extract:
- Implementation Plan: Task checkboxes organized by layer (Frontend, Backend, Database, Testing)
- Technical Context: Architecture decisions, API contracts, schema changes
- Decision Record path: Read the referenced decision record for full council context
- Feature Flag: Flag name if applicable
- Success Metrics: Measurable outcomes
-
Read the referenced decision record from the path specified in the issue for complete council rationale.
-
Signal work is in progress (see AGENTS.md "Label Management" for rules):
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.
- 10d ago First seen · 443 lines · 52 tokens per session scan A 98f42107aa67
build-feature is a skill published in the GitHub repository andrewvaughan/agent-council (13 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 3,904 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
summarize-transcript
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear actionable document.