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 skills/nmrtn/nanopm/pm-competitors-intelnpx skills add nmrtn/nanopm --skill pm-competitors-intelgit clone --depth 1 https://github.com/nmrtn/nanopmWrote 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/nmrtn/nanopm/pm-competitors-intel)<a href="https://agentmods.dev/skills/nmrtn/nanopm/pm-competitors-intel"><img src="https://agentmods.dev/badge/skills/nmrtn/nanopm/pm-competitors-intel.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 | $0.00060 | $0.06966 |
| Opus 5 | $0.00030 | $0.03483 |
| Sonnet 5 | $0.00012 | $0.01393 |
| Haiku 4.5 | $0.00006 | $0.00697 |
Grade E, and why
pm-competitors-intel scanned grade E with 3 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 4d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; } Cloud metadata endpointhighServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- Every URL MUST be a public `https://` web address. Never propose `http://`, a raw IP, `localhost`, a cloud metadata endpoint (e.g. 169.254.169.254), or any private/internal host — these get fetched later, so an attacke Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; } How it starts
The opening of the file, as written. The whole thing — 586 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-host portability rules. When invoking
AskUserQuestion:
- The
headerfield MUST be a short noun phrase (≤ 12 characters). Mistral Vibe rejects longer headers withstring_too_long. Pick from:Start,Target,Scope,Audience,Methodology,Feature,Question.- The
optionslist MUST have at least 2 items. Vibe rejects empty/single-option calls. For free-text input, always provide ≥ 2 framing options (e.g.Yes, here's the input/Skip) — never callask_user_questionwithoptions: [].
Preamble (run first)
source ~/.nanopm/lib/nanopm.sh 2>/dev/null || \
source .nanopm/lib/nanopm.sh 2>/dev/null || \
{ echo "ERROR: nanopm not installed. Run: curl -fsSL https://raw.githubusercontent.com/nmrtn/nanopm/main/setup | bash"; exit 1; }
nanopm_preamble
_INTEL_DIR=".nanopm/raw/competitors"
_SNAPSHOT_DIR=".nanopm/raw/competitors/snapshots"
_COMPETITORS_FILE=".nanopm/raw/competitors/competitors.json"
mkdir -p "$_INTEL_DIR" "$_SNAPSHOT_DIR"
# Mode routing. The default run is the cheap diff veille (one diff subagent).
# An "analyze" keyword in the skill arguments preselects the heavy analysis
# (SWOT + positioning matrix). Phase 1 also offers the same mode via menu, so
# both paths converge on _MODE=analyze. With no keyword and no menu choice,
# _MODE stays "diff" — behaviour is unchanged, no extra agents, no cost regression.
_MODE="diff"
case "$(echo "${ARGUMENTS:-}" | tr '[:upper:]' '[:lower:]')" in
*analyze*|*analyse*|*deep*|*landscape*) _MODE="analyze" ;;
esac
echo "MODE: $_MODE"
Phase 0: Prior context
source ~/.nanopm/lib/nanopm.sh 2>/dev/null || source .nanopm/lib/nanopm.sh 2>/dev/null || true
nanopm_context_read pm-competitors-intel
If a prior entry exists, show: "Last intel run: {ts}. Checking for changes since then."
Pull the Define/Plan context through the query primitive so the report compares us-vs-them on real positioning instead of a guess — one read-side call that synthesizes the relevant wiki pages instead of bespoke per-doc reads (the recipe pattern: query → reasoning → ingest). The raw docs stay out of this run; you reason over the cited synthesis the query returns. Print the prompt and dispatch it with the Agent tool (one subagent); on a host with no Agent tool, follow its steps inline.
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.
- 4d ago First seen · 586 lines · 60 tokens per session scan E e1488ba9c1b2
pm-competitors-intel is a skill published in the GitHub repository nmrtn/nanopm (48 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 6,966 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it E with 3 findings (downloads and executes remote code, cloud metadata endpoint, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…