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 skills add marfoerst/the-pragmatic-pm --skill pm-productboard-insightsgit clone --depth 1 https://github.com/marfoerst/the-pragmatic-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/skills/marfoerst/the-pragmatic-pm/pm-productboard-insights)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-productboard-insights"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-productboard-insights/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/marfoerst/the-pragmatic-pm/pm-productboard-insights"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-productboard-insights.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.00141 | $0.02883 |
| Opus 5 | $0.00071 | $0.01442 |
| Sonnet 5 | $0.00028 | $0.00577 |
| Haiku 4.5 | $0.00014 | $0.00288 |
Grade A, and why
pm-productboard-insights scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST https://api.productboard.com/v2/notes \ How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Productboard Insights from Transcripts
You turn a raw transcript into structured customer Insights and file them in Productboard. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context, and read personal-context.md if available for the user's role and preferences. Adapt all outputs — product-area names, tags, terminology — to match that context.
Core Principle
An Insight is evidence, captured in the customer's own words — not your interpretation of it. One transcript yields many insights; each is atomic (one demand per insight), verbatim (the quote is preserved, not paraphrased away), and attributed (who said it, which customer/company). Your job is to lift the signal cleanly and file it where the product team will find it — not to decide the roadmap. Resist editorializing: "User wants bulk export" is weaker evidence than the quote that produced it.
A demand is anything the customer expresses a need, friction, desire, or constraint about — even when phrased as praise ("the one thing I'd never give up is...") or as a workaround ("so I just export to Excel and do it by hand"). Capture all of these.
Phase 0: Preflight — the Notes API (do this first, before extracting anything)
Critical: In Productboard, "Insights" are stored as Notes, and notes are created through the Notes API — POST https://api.productboard.com/v2/notes with a Bearer token. The official Productboard MCP (https://mcp.productboard.com) is spec-centric (search/read/edit specs, comment, update status) and cannot create insights; use it only, and optionally, to resolve which feature an insight should link to.
This skill writes via the Notes API + token. Preflight:
- Get the token. Read it from the
PRODUCTBOARD_API_TOKENenvironment variable. If it's not set, ask the user to provide it (a Productboard public API token) and to export it for the session —export PRODUCTBOARD_API_TOKEN=…. Never paste, echo, log, or hardcode the token into files or commands; reference it only as$PRODUCTBOARD_API_TOKEN. - Verify access with a cheap read —
GET https://api.productboard.com/v2/notes?pageLimit=1with theAuthorization: Bearer $PRODUCTBOARD_API_TOKENandX-Version: 1headers. A 200 confirms the token and the workspace it belongs to. On 401, stop and ask for a valid token before going further. - If a token can't be obtained, fall back to draft-only: produce the structured insights for manual paste and say clearly that nothing was filed.
- (Optional) feature linking. If the official spec MCP is connected, you may search specs to resolve link targets — reads only during preflight, create/modify nothing.
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 · 167 lines · 141 tokens per session scan A c850fa89ba81
pm-productboard-insights is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 141 tokens to every session and 2,883 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
forge-execute
Guided plan execution — list available plans, estimate cost, choose mode, and execute with live progress. Use when you want to run a hardened plan through the orchestrator.
non-engineering-verticals
C-suite personas, compliance OS, PM domain, and finance domain skills for enterprise client work. Activates when client conversations shift from code to strategy, compliance, product, or financial modeling. Source: alirezarezvani/claude-skills C-suite + compliance tier.
source-command-cycle
Execute continuous development cycle for an epic.
source-command-story
Generate implementation stories from planning documents.
source-command-plan
Generate scale-adaptive planning documents (PRD and architecture).
Block Close
Update block documentation after completing work on a feature block. Run this after finishing work to close the feedback loop.