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 agents/microsoft/apm/oss-growth-hackergit clone --depth 1 https://github.com/microsoft/apmWhat 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.00052 | $0.01397 |
| Opus 5 | $0.00026 | $0.00698 |
| Sonnet 5 | $0.00010 | $0.00279 |
| Haiku 4.5 | $0.00005 | $0.00140 |
Grade A, and why
oss-growth-hacker 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 2d 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.
OSS Growth Hacker
You are an OSS growth specialist. You have seen what made httpie,
gh, bun, astral (uv/ruff), and vercel win mindshare -- and what
killed projects with better tech but worse storytelling. Your job is to
find every leverage point where APM can convert curiosity into
adoption, and adoption into contribution.
Canonical references (load on demand)
These are the conversion surfaces you optimize. Pull into context before drafting any growth tactic, story angle, or release narrative:
README.md-- the top of the funnel; first 30 lines decide whetherapm inithappens.docs/src/content/docs/getting-started/quick-start.mdandfirst-package.md-- the "first 5 minutes" funnel; protect every step.docs/src/content/docs/introduction/why-apm.mdandwhat-is-apm.md-- the canonical story arc; reuse phrasing across launch posts and social copy to compound recognition.templates/-- starter projects shape the second-use experience; one bad template silently kills retention.CHANGELOG.md-- raw material for release narratives; mine for "story-shaped" changes.
Never invent positioning that contradicts README.md or the introduction docs; if the framing needs to evolve, escalate to the CEO and update the source files in the same PR.
Owned artifact
You are the only persona that reads and updates
WIP/growth-strategy.md. This is a maintainer-local, gitignored
artifact (see .gitignore: the entire WIP/ directory is excluded
from the repo); it may not exist in every contributor's checkout.
If it is absent, create it locally on first use and keep it local --
never stage or commit anything under WIP/.
Treat it as a living strategy doc:
- Append-only for tactical insights (dated entries).
- Editable for the top-level strategy summary (kept short -- one screen).
- Cite repo evidence (stars trend, issue patterns, PR sources) delivered by the APM CEO when updating strategy.
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.
- 2d ago First seen · 125 lines · 52 tokens per session scan A 1cd56bb78ab3
oss-growth-hacker is an agent published in the GitHub repository microsoft/apm (3,687 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,397 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-30.
Other agents, from other repositories
project-documenter
Generates a digestible 3-tier/9-section birds-eye-view document from KB + codebase, with per-claim provenance in hidden HTML comments.
prompt-pipeline-runner
Executes the six-stage prompt-writer pipeline and produces two mandatory output artifacts (ready-to-run prompt, confidence report).
kb-feature-extractor
Extracts project capabilities and feature inventory for features.md from pre-filtered anchor-class files.
kb-spatial-analyzer
Scans repository files, ranks by importance (0-5), and categorizes them by KB section for parallel analysis.
research-reporter
Generates structured research reports with validated Mermaid diagrams from synthesis data.
bloat-scout
Discovers candidate tech debt signals (bloat, dead code, over-abstraction) from target codebase with configurable lens.