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/asisaga/linkedin.asisaga.com/spec-managernpx skills add ASISaga/linkedin.asisaga.com --skill spec-managergit clone --depth 1 https://github.com/ASISaga/linkedin.asisaga.comWrote 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/asisaga/linkedin.asisaga.com/spec-manager)<a href="https://agentmods.dev/skills/asisaga/linkedin.asisaga.com/spec-manager"><img src="https://agentmods.dev/badge/skills/asisaga/linkedin.asisaga.com/spec-manager.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.00886 |
| Opus 5 | $0.00023 | $0.00443 |
| Sonnet 5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
spec-manager 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 3d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Manager
Role: Specification Engineer for SDD Workflow
Scope: specs/, .github/specs/, .github/templates/
Version: 1.1
Purpose
Implement the Specification-Driven Development (SDD) workflow through three agent-driven stages that transform plain-language descriptions into structured, executable specifications.
→ SDD principles: .github/specs/spec-driven-development.md
→ Full methodology: .github/docs/spec-driven.md
When to Use This Skill
Activate when:
- A new feature needs a structured specification
- An existing spec needs to be validated or refined
- An implementation plan needs to be generated from a spec
- A task list needs to be derived from a plan
Three SDD Workflows
| Stage | Prompt | Output |
|---|---|---|
| 1. Specify | spec-create.prompt.md |
specs/NNN-slug/spec.md |
| 2. Plan | spec-plan.prompt.md |
plan.md, research.md, data-model.md, contracts/, quickstart.md |
| 3. Tasks | spec-tasks.prompt.md |
specs/NNN-slug/tasks.md |
Core Principles (from SDD)
Spec-First: Specifications drive code, not the reverse
Clarify, Don't Guess: Mark all ambiguities with [NEEDS CLARIFICATION]
Constitutional Gates: Enforce Articles III, VII, VIII, IX before planning
Test-First Ordering: Contract tests → integration tests → implementation
Validation Scripts
1. Spec Validation
./.github/skills/spec-manager/scripts/validate-spec.sh specs/<NNN>-<slug>/spec.md
# Checks:
# - No [NEEDS CLARIFICATION] markers remain
# - Required sections are present
# - User stories have role/goal/benefit
# - Acceptance criteria are measurable
2. List Specs
./.github/skills/spec-manager/scripts/list-specs.sh
# Shows:
# - All feature directories in specs/
# - Status of spec.md, plan.md, tasks.md
# - Next available feature number
3. Create Feature Branch
./.github/skills/spec-manager/scripts/create-feature-branch.sh "<description>"
# Creates:
# - git branch NNN-kebab-slug
# - specs/NNN-kebab-slug/ directory
What ships with it
3 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.
- 3d ago First seen · 112 lines · 47 tokens per session scan A f0ce25cb15e9
spec-manager is a skill published in the GitHub repository ASISaga/linkedin.asisaga.com (0 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 886 once invoked, about $0.0002 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-31.
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…