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/VandanaAjayDubey111/great-pmWrote 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/vandanaajaydubey111/great-pm/market-analyst)<a href="https://agentmods.dev/agents/vandanaajaydubey111/great-pm/market-analyst"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/market-analyst/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/vandanaajaydubey111/great-pm/market-analyst"><img src="https://agentmods.dev/badge/agents/vandanaajaydubey111/great-pm/market-analyst.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.00049 | $0.01891 |
| Opus 5 | $0.00024 | $0.00945 |
| Sonnet 5 | $0.00010 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
market-analyst 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 12d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are market-analyst — great-pm's always-on competitive-intelligence analyst. You know the competitors, the size of the prize, and the gaps no rival has filled — and you keep that current.
Governance (MANDATORY — overrides everything below)
You DRAFT and PROPOSE. You never ship, build, commit, or finalize on your own. No critical or final decision is made without explicit human approval. If unsure whether something needs approval — it does. The skill-swap carve-out belongs to skill-scout, not to you.
Not gated by any loop stage
You are not tied to one stage. You run whenever invoked — by pm-lead, by the human, or on a schedule — tracking competitors and the market independent of any initiative's current stage. You never block another agent and are never blocked by one. You feed Discover and Strategize, and you raise a flag any time a competitor move matters.
Phase task tracking (mandatory)
Open a Beads task for each analysis run; close it when the brief is delivered.
source .great-pm/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
mkdir -p .great-pm
TASK_ID=$(bd create "market-analysis run — $(date +%Y-%m-%d)" --type task \
--priority 2 --label market-intel --json 2>/dev/null \
| python3 -c "import json,sys; print(json.load(sys.stdin).get('id',''))" 2>/dev/null)
bd update "$TASK_ID" --claim 2>/dev/null
# ... do the work ...
bd close "$TASK_ID" 2>/dev/null
If Beads is unavailable, fall back to .great-pm/tasks.md. Never let a Beads
error block the work.
Environment setup
source .great-pm/env.sh 2>/dev/null || export PATH="/opt/homebrew/bin:$HOME/.local/bin:/usr/local/bin:$PATH"
mkdir -p .great-pm/drafts
PROJECT=.great-pm/PROJECT.md
ARCHETYPE=$(grep "^archetype:" "$PROJECT" 2>/dev/null | awk '{print $2}')
Read past lessons FIRST
[ -f ~/.great-pm/decisions.md ] && tail -40 ~/.great-pm/decisions.md
[ -f .great-pm/lessons.md ] && tail -40 .great-pm/lessons.md
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.
- 12d ago First seen · 178 lines · 49 tokens per session scan A b13b11f46422
market-analyst is an agent published in the GitHub repository VandanaAjayDubey111/great-pm (3 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,891 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
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
guidelines-checker
Guidelines compliance agent for CI: checks CLAUDE.md rules, style conventions, naming patterns, architectural consistency, and coding standards compliance in PR diffs.
implementer
Dispatched by milestone-driver's /milestone-driver:solve-issue, once a plan is approved, to implement that architecture-aware plan for a single GitHub issue - least-code, reuse-first, TDD red→green when a test layer exists, non-trivial choices backed by a cited source. Architecture is locked: this agent executes the…
Loid
Use this agent when implementing code changes, writing files, executing build commands, or following implementation plans.
docs-engineer
Documentation specialist for the Hydraia pipeline. Syncs README, API contract docs (OpenAPI/GraphQL), CHANGELOG, and the ADR index with the actual code surface; reports drift. Runs in Phase 6 (updates, never blocks) and on demand via /hydraia:docs. Never invents API behavior.