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 agentmods add skills/bodangren/git-workflow/spec-authoringnpx skills add bodangren/git-workflow --skill spec-authoringgit clone --depth 1 https://github.com/bodangren/git-workflowWhat 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 | $0.00053 | $0.01117 |
| Opus 5 | $0.00026 | $0.00558 |
| Sonnet 5 | $0.00011 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
spec-authoring 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 2d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Authoring Skill
Purpose
To manage the creation and refinement of feature specifications using a powerful, AI-assisted workflow. This skill leverages the Gemini CLI to accelerate the spec-driven development process by:
- Generating Drafts: Automatically creates high-quality, multi-file draft proposals for new features.
- Analyzing Feedback: Synthesizes review comments from Pull Requests into an actionable summary of recommended changes.
This approach allows developers and product managers to move from idea to an approved, implementation-ready specification with greater speed and clarity.
When to Use
Use this skill in the following situations:
- Proposing a new feature or significant change.
- Generating a first draft of a specification for review.
- Processing and incorporating feedback from a Spec PR.
Prerequisites
- Project initialized with AgenticDev structure (
docs/specs/anddocs/changes/directories exist). - GitHub repository set up.
ghCLI tool installed and authenticated.geminiCLI tool installed and authenticated.
Spec PR Philosophy
Specs as Code: All specification changes follow the same rigor as code changes—proposed via branches, reviewed via PRs, and merged upon approval. This skill supercharges that philosophy with AI.
The propose Command
Purpose
Generate a comprehensive, multi-file draft proposal for a new feature from a single command.
Workflow
Step 1: Define the Proposal Name
Choose a clear, descriptive name for your feature, such as "User Authentication System" or "Real-time Notifications".
Step 2: Run the Helper Script
Execute the script to generate the draft proposal:
bash scripts/spec-authoring.sh propose "Feature Name"
The script will:
- Create a new directory in
docs/changes/feature-name/. - Make three parallel calls to the Gemini CLI to generate drafts for
proposal.md,spec-delta.md, andtasks.md.proposal.md: A high-level overview with problem statement, proposed solution, and success criteria.spec-delta.md: A detailed technical specification with requirements and design decisions.tasks.md: A preliminary breakdown of implementation tasks.
- Save the AI-generated content into these files.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 125 lines · 53 tokens per session scan A f1c8dd9013bf
spec-authoring is a skill published in the GitHub repository bodangren/git-workflow (11 stars, last pushed 9mo ago), licensed MIT. It adds 53 tokens to every session and 1,117 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…