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 rules/perniemann/pncore/mcp-only-bootstrapgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/rules/perniemann/pncore/mcp-only-bootstrap)<a href="https://agentmods.dev/rules/perniemann/pncore/mcp-only-bootstrap"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/mcp-only-bootstrap.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.00436 | $0.00436 |
| Opus 5 | $0.00218 | $0.00218 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
mcp-only-bootstrap 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 3d 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.
What it actually says
pn-core MCP-only bootstrap
Start every new chat with: [pn-default] ▲ (context tag + Unicode U+25B2). Do this before any other output or tool call.
Requires pn-core MCP. If build/design flows do not trigger, pn-core may not be configured. Add to ~/.cursor/mcp.json (user) or .cursor/mcp.json (project). From pnCore repo: npm run mcp-config. See docs/mcp-usage-guide.md.
When pn-core MCP is available, load and follow the canonical pn rules so build/design and skill use behave like the full plugin.
First action in the session (or when the user gives a build/design/fix request):
- Call
get_rule("pn-build-gate")and follow it (useworkflow_steporget_commandfor build/design; use skills directly for fix/tweak). - Call
get_rule("pn-mcp-proactive")and follow it (uselist_skills/get_skill,list_agents/get_agent,list_commands/get_commandwhen the task matches a pn id).
You do not have the plugin's file-based rules in this workspace, so you must load these two rules via MCP and apply them. After that, proceed as the rules specify.
Continual learning: The skill pn-continual-learning is available via get_skill("pn-continual-learning"). When the user asks to "update AGENTS.md from transcripts" or "run continual learning", load that skill and follow its workflow (read transcripts, extract preferences/facts, merge into AGENTS.md). Automatic run-on-stop requires the plugin's hook and script; MCP-only, run the skill when the user asks.
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.
- 3d ago First seen · 22 lines · 436 tokens per session scan A 2d04cdfe9f6e
mcp-only-bootstrap is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed yesterday), licensed MIT. It adds 436 tokens to every session, about $0.0022 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 cursor rules, from other repositories
1001-typescript
APPLY TypeScript best practices WHEN writing code TO ensure type safety, readability, and maintainability.
nauro-ship-task
Run the full planner -> executor -> reviewer -> tech-lead -> direct-user-confirm -> push chain through Cursor's native project workflow agents. Requires the four bundled .cursor/agents/nauro-.md definitions and fails closed without native dispatch.
aim
The aim of this project is to port the adk-python implementation to TypeScript (adk-ts). When porting code.
frontend
Frontend specific rules.
000-writing-style
ENFORCE when WRITING DOCUMENTATION to ELIMINATE LLM-GENERATED PATTERNS.
702-aws-well-architected-framework
Apply AWS Well-Architected Framework pillars when designing or reviewing AWS solutions.