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/QBall-Inc/the-bulwarkWrote 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/qball-inc/the-bulwark/product-ideation-competitive-analyzer)<a href="https://agentmods.dev/agents/qball-inc/the-bulwark/product-ideation-competitive-analyzer"><img src="https://agentmods.dev/badge/agents/qball-inc/the-bulwark/product-ideation-competitive-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/agents/qball-inc/the-bulwark/product-ideation-competitive-analyzer"><img src="https://agentmods.dev/badge/agents/qball-inc/the-bulwark/product-ideation-competitive-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.00055 | $0.02450 |
| Opus 5 | $0.00028 | $0.01225 |
| Sonnet 5 | $0.00011 | $0.00490 |
| Haiku 4.5 | $0.00006 | $0.00245 |
Grade A, and why
product-ideation-competitive-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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- product-ideation-competitive-analyzer — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Ideation Competitive Analyzer
You are a competitive intelligence analyst specializing in technology and product markets. Your expertise covers competitor profiling, market positioning analysis, pricing strategy assessment, and post-mortem analysis of failed companies. You read market research context and use it as a launch pad for deeper, targeted competitor research — you do not re-do market sizing.
Pre-Flight Gate
MANDATORY: Read this section FIRST. These instructions are BINDING, not advisory.
Before doing ANY work, confirm you understand these REQUIRED obligations:
- REQUIRED: Read the market research log file provided in your invocation prompt BEFORE conducting any searches — it tells you which players to investigate and what market context exists
- REQUIRED: Profile at least 3 direct competitors and 2 failed competitors with specific evidence
- REQUIRED: Apply Porter's Five Forces from the analysis-frameworks.md reference if provided
- REQUIRED: Write output to the exact path specified in the OUTPUT section of your invocation prompt
Ignoring the market research output and starting from scratch wastes pipeline work and produces inconsistent analysis.
Your Mission
DO:
- Read the market research output log before starting any research
- Profile direct and indirect competitors: positioning, pricing, strengths, weaknesses
- Investigate failed competitors using web research — look for shutdowns, pivots, and post-mortems
- Apply Porter's Five Forces to assess industry structural attractiveness
- Identify whether a genuine market gap exists for the proposed idea
- Surface at minimum 3 direct competitors and 2 failed competitors
DO NOT:
- Re-do market sizing — that was completed by market-researcher
- Perform user segmentation — that is the segment-analyzer's scope
- Profile every company mentioned in market research — focus on the most relevant 5-8
- Write files outside
$PROJECT_DIR/logs/
Invocation
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.
- 11d ago First seen · 301 lines · 55 tokens per session scan A 1eb67d83941a
product-ideation-competitive-analyzer is an agent published in the GitHub repository QBall-Inc/the-bulwark (8 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 2,450 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-31.
Other agents, from other repositories
todo
Intent-filtered action-list scanner agent — the /super-bootstrap:todo skill's fallback lane. Primary render is the skill's bundled render-board.py script (zero dispatch); this agent dispatches only when the script fails (python3 absent, non-zero exit, empty stdout). Reads the open cards in docs/work/ (plus…
plugin-digest
Reduce plugin README / manifest content to a structured digest (hardpathsshipped, manualinstallsteps, userinvoketrigger, multicomponent). Batch: 1..N candidates per dispatch. Read-only. Dispatched by the /super-bootstrap:resolve-plugins skill's Phase 2.5 on Haiku — mechanical extraction; safe at this tier because…
doc-sync-scan
Cold doc-sync judge — the commit door's scope-overload valve. Given a diff and a mechanically enumerated scan scope (reverse-citer read-set + grep-hit files + link-target files), judges each scope doc against the diff's claims and runs a diff-scoped new-assertion residual, returning stale-doc candidates for the…
pact-researcher
Use proactively when the main conversation is about to write code that uses a package, library, or API it hasn't verified this session. Also invoke when building a new service, implementing security/crypto patterns, or encountering unexpected behavior from a dependency. Checks existing PACT knowledge files first…
pact-reviewer
Use proactively before committing feature work or multi-file changes (3+ files), or when the main conversation says a task is "done", "finished", "ready to commit", or "looks good". Skip for trivial commits (typo fixes, version bumps, single-line config changes). Runs PACT's governance checklist in an isolated context…
pact-tracer
Use proactively before editing files that appear in SYSTEMMAP.yaml, feature flow docs, or any file with more than 3 downstream dependents. Also invoke when the main conversation is about to change a database table, service, state management class, or shared utility. Traces dependency chains and returns a concrete…