Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add nguyenvanphituoc/shapeup-sdlc-plugin/plugin install shapeup-sdlc-pluginWrote 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/nguyenvanphituoc/shapeup-sdlc-plugin/ba-pitch-analyzer)<a href="https://agentmods.dev/skills/nguyenvanphituoc/shapeup-sdlc-plugin/ba-pitch-analyzer"><img src="https://agentmods.dev/badge/skills/nguyenvanphituoc/shapeup-sdlc-plugin/ba-pitch-analyzer/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/nguyenvanphituoc/shapeup-sdlc-plugin/ba-pitch-analyzer"><img src="https://agentmods.dev/badge/skills/nguyenvanphituoc/shapeup-sdlc-plugin/ba-pitch-analyzer.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.00142 | $0.03342 |
| Opus 5 | $0.00071 | $0.01671 |
| Sonnet 5 | $0.00028 | $0.00668 |
| Haiku 4.5 | $0.00014 | $0.00334 |
Grade A, and why
ba-pitch-analyzer 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BA Pitch Analyzer (spec-analyzer, pure worker v4.0)
Decompose the pitch into a spec a machine can build and a judge can grade — invent nothing.
Converts a Shape Up pitch (or any product requirement) into a fully linked document tree:
_index → domain-model → ux-behavior → usecases/ → integration → tasks/ — Obsidian
wikilinks + shared frontmatter taxonomy, navigable from pitch to atomic task.
You are the planner in a planner → doer → judge harness, and a pure worker: the order tells you which operation to run and which files you may write; you return everything else as data. You keep no state — no run-state.md, no pitch-hash cache, no counters. Same order in → same artifacts out.
Input contract — the WorkOrder
Invoked as --order <path>. Fields you may rely on (absent = unknown; surface it, never guess):
| Field | What it is |
|---|---|
operation |
analyze (pitch → full spec tree + board) · reconcile (fold discovered-ledger items into the board + UC invariants) · retrofit-surface (append ## Test Surface to a pre-surface spec) · coverage (extract atomic requirement clauses → the SHARED requirements.md registry) |
payload.pitch |
The pitch/PRD path (analyze) |
payload.requirements |
(coverage) the REQ source to extract atomic clauses from — pitch / a customer-requirements doc / the use-case bodies. Absent → default to the pitch and record the choice in assumptions[] |
payload.lens |
lite | standard | cross-context. Absent → judge it: LITE for ≤2-week appetite, no third-party, ≤3 user-facing actions; STANDARD for multi-team, third-party, or bigger appetite; genuinely unclear → one binary question, or status: "escalated" with the question in deviations[] |
payload.orient_dir |
The Scout's artifacts — code-surface.md IS your codebase map (do not re-scan), discovered-seed.md seeds task gen, spike-*.md feeds feasibility |
payload.spec_folder / payload.feature |
Where the committed tree lives / the slug |
payload.discovered_ledger |
(reconcile) the ledger whose raw [+]/~ lines you fold in |
payload.kb_rules_path |
Team guidelines (read if present) — steering, never spec |
substrate.allowed / append_only / frozen |
Your write contract for THIS operation. The old frozen-zone prose is now data the sandbox hook enforces (reading the order's envelope): respect it, and when an operation genuinely needs a file outside it, ESCALATE — never widen |
interaction.pause_gates |
Caller policy. true (standalone default): pause at the phase checkpoints below, max 2 questions each. false: run straight through, surfacing questions as assumptions[] (or deviations[] when they block) instead |
What ships with it
28 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.
- assets/templates/_index.tmpl.md 1.9 KB
- assets/templates/api-feasibility.tmpl.md 2.6 KB
- assets/templates/assess-report.tmpl.md 3.1 KB
- assets/templates/contracts/be-service.contract.tmpl.md 2.0 KB
- assets/templates/contracts/offline-storage.contract.tmpl.md 2.6 KB
- assets/templates/contracts/third-party-api.contract.tmpl.md 2.4 KB
- assets/templates/cross-context/context-map.tmpl.md 2.2 KB
- assets/templates/cross-context/event-choreography.tmpl.md 2.5 KB
- assets/templates/cross-context/migration-plan.tmpl.md 2.8 KB
- assets/templates/cross-context/team-handoff.tmpl.md 2.9 KB
- assets/templates/domain-model.tmpl.md 1.7 KB
- assets/templates/feedback.tmpl.md 2.2 KB
- assets/templates/integration.tmpl.md 1.3 KB
- assets/templates/run-state.tmpl.md 2.0 KB
- assets/templates/scope-summary.tmpl.md 2.9 KB
- assets/templates/synthesis.tmpl.md 6.9 KB
- assets/templates/task-board.tmpl.md 884 B
- assets/templates/task-spike.tmpl.md 2.6 KB
- assets/templates/task.tmpl.md 3.6 KB
- assets/templates/usecase.tmpl.md 3.3 KB
- assets/templates/ux-behavior.tmpl.md 1.4 KB
- references/contract-patterns.md 5.4 KB
- references/ddd-patterns.md 5.4 KB
- references/doc-schemas.md 8.9 KB
- references/integration-analysis.md 4.4 KB
- references/task-generation.md 25 KB
- references/test-surface.md 6.5 KB
- references/ux-behavior-patterns.md 10 KB
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 · 181 lines · 142 tokens per session scan A a40e391caf6b
ba-pitch-analyzer is a skill published in the GitHub repository nguyenvanphituoc/shapeup-sdlc-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 142 tokens to every session and 3,342 once invoked, about $0.0007 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
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.
cog-team-intelligence
Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.
agentrq
Lead multiple agents to accomplish big tasks with specialized workspaces/agents by assigning tasks to specialized agents.
agentrq
Execute tasks assigned by humans or supervisor agents within a specific AgentRQ workspace. Use when you receive channel messages or need to report progress on tasks.
swarm-orchestration
Multi-agent swarm formation and coordinated execution with topology-aware agent deployment, consensus protocols, and anti-drift enforcement.