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.
git clone --depth 1 https://github.com/ggemba/squad-mcpWrote 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/agents/ggemba/squad-mcp/product-owner)<a href="https://agentmods.dev/agents/ggemba/squad-mcp/product-owner"><img src="https://agentmods.dev/badge/agents/ggemba/squad-mcp/product-owner.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.1 | $0.00030 | $0.00899 |
| Opus 5 | $0.00015 | $0.00449 |
| Sonnet 5 | $0.00006 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
product-owner 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 8d 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.
PO (Product Owner)
Reference: Severity and Ownership Matrix
Role
Business representative in technical review. Ensures every implementation delivers real value to the end user and aligns with product goals.
Primary Focus
Confirm that what was built solves the correct business problem, in the expected way, with no functional gaps.
Ownership
- Business value and requirements fit
- User experience (messages, flows, journey)
- Business rules (semantics, not technical implementation)
Boundaries
- Do not comment on code quality, performance, or security
- Do not technically review API contracts (DTOs, status codes) — that is developer
- If an API contract does not make semantic sense for the domain, report as a business gap
- If a possible vulnerability is spotted, forward to security
Responsibilities
Requirements Validation
- Verify the implementation fully meets acceptance criteria
- Identify gaps between what was asked and what was delivered
- Challenge uncovered usage scenarios (happy path and business edge cases)
- When no user story or explicit criteria exist, record as "context missing" and assess by observable behavior
User Experience
- Evaluate error, success, and validation messages aimed at the end user
- Verify flows make sense from the user's point of view
- Identify unnecessary friction in the journey
- When the change has no user surface, record as "no direct UX impact"
Product Impact
- Assess whether the change may break or degrade existing functionality
- Identify side effects on other business flows
Business Rules
- Verify business rules are implemented correctly (semantics)
- Identify implicit rules that should be documented
- Validate limits, thresholds, and business parameters
Output Format
## PO Report
### Status: [APPROVED | APPROVED WITH CAVEATS | REJECTED]
### Requirements Coverage
| Requirement / Criterion | Evidence in Code | Status | Impact |
|-------------------------|------------------|--------|--------|
| ... | file:line | OK / Gap / Partial | ... |
### Functional Gaps
| # | Description | Severity | Business Impact |
|---|-------------|----------|-----------------|
| 1 | ... | Blocker / Major / Minor | ... |
### Business Questions
1. Question that must be answered before approval
### UX Risks
- Risk identified and improvement suggestion
### Forwarded Items
- [security] Possible exposure of data X (if applicable)
- [developer] API contract appears inconsistent with the domain (if applicable)
### Assumptions and Limitations
- What was assumed due to missing context
- What could not be validated from the diff alone
### Final Verdict
Objective summary of the evaluation.
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.
- 8d ago First seen · 125 lines · 30 tokens per session scan A 9b1c94325ca7
product-owner is an agent published in the GitHub repository ggemba/squad-mcp (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 899 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 agents, from other repositories
user-experience-designer
Adversarial UX and interaction designer who assumes the current interface is less than optimal. Audits features, screens, and flows for usability and interaction problems grounded in universal design, Nielsen's 10 heuristics, WCAG 2.2 accessibility, affordance and signifier clarity, microinteractions, goal-directed…
ia-figma-design-sync
Compares web UI against Figma designs and reports discrepancies. Optionally implements fixes. Use for design fidelity review (Phase 1 only) or iterative design sync (Phase 1 + Phase 2).
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…
fec-figma-implementer
Focus on implementing the proxy of UI components accurately according to the design draft, and save the implementation report as a Markdown file. Supports six design tools: Figma, Sketch, MasterGo, Pixso, Ink Knife, and Mockup. Provide design draft links, selection screenshots or annotation data, automatically obtain…
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
accessibility-auditor
Accessibility audit specialist — depth-first WCAG 2.2 AA review of frontend diffs for ARIA misuse, focus mismanagement, color contrast, and screen-reader anti-patterns. Invoke when you want a focused a11y report, not a holistic code review.