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 instructions/saagpatel/portfolio-mcp/agents-mdgit clone --depth 1 https://github.com/saagpatel/portfolio-mcpWrote 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/instructions/saagpatel/portfolio-mcp/agents-md)<a href="https://agentmods.dev/instructions/saagpatel/portfolio-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/saagpatel/portfolio-mcp/agents-md.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.00324 | $0.00324 |
| Opus 5 | $0.00162 | $0.00162 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
portfolio-mcp AGENTS.md 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
Portfolio Context
What This Project Is
portfolio-mcp: The agent-native layer of saagarpatel.dev: a Model.
Current State
- Built + locally verified: Layers 0–2. Shared core + 8 tools + Resources + 2 prompts +
get_operant_results. typecheck clean; test suite passes (incl. full MCP protocol via the fetch handler). Live Worker probe and deploy remain operator-gated. Public discovery advertisesmcp.saagarpatel.devwith a valid Ed25519-signed manifest. - Gated / next: publish the stdio package (
npm publish, after removing"private": trueby explicit operator approval only), glama.ai registry listing, and continued signed-manifest readback checks after website manifest changes.
Stack
- Primary stack: Node.js, TypeScript
- JavaScript package manager: npm-compatible workflow
How To Run
- Install dependencies with
npm install. - Start local development with
npm run dev. - Review the repo README for any required verification commands before shipping.
Known Risks
- This repo only has minimum-viable recovery context today; deeper handoff details may still live in the README and supporting docs.
Next Recommended Move
Use this context plus the README and supporting docs to resume the next active task, then promote the repo beyond minimum-viable by capturing a dedicated handoff, roadmap, or discovery artifact.
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 · 38 lines · 324 tokens per session scan A 9f00c980809a
portfolio-mcp AGENTS.md is an instructions file published in the GitHub repository saagpatel/portfolio-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 324 tokens to every session, about $0.0016 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 instructions, from other repositories
ctxlayer CLAUDE.md
Claude Code instructions for stevenn/ctxlayer, covering ctxlayer — claude code briefing, what runs where, architecture pointers, how a claude session should work in this repo and conventions.
sbb-opendata-mcp CLAUDE.md
Claude Code instructions for malkreide/sbb-opendata-mcp, covering claude.md, teil 1 — konventionen (portfolio-weit), vor der arbeit, tests and wenn etwas rot ist.
ctxlayer AGENTS.md
AGENTS.md instructions for stevenn/ctxlayer, covering working in this repo as an agent, golden path for any change, where things live, module rules and adding an endpoint.
sidewise CLAUDE.md
Claude Code instructions for nulljosh/sidewise, covering sidewise, architecture, endpoints, develop and tests.
bible-mcp AGENTS.md
AGENTS.md instructions for tuxr/bible-mcp, covering agents.md, live urls, commands, architecture and current tools & prompts.
swiss-snb-mcp CLAUDE.md
Claude Code instructions for malkreide/swiss-snb-mcp, covering claude.md, teil 1 — konventionen (portfolio-weit), vor der arbeit, tests and wenn etwas rot ist.