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/justinmclean/podlingsmcp/agents-mdgit clone --depth 1 https://github.com/justinmclean/PodlingsMCPWrote 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/justinmclean/podlingsmcp/agents-md)<a href="https://agentmods.dev/instructions/justinmclean/podlingsmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/justinmclean/podlingsmcp/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.00467 | $0.00467 |
| Opus 5 | $0.00234 | $0.00234 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
PodlingsMCP 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 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.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
Purpose
This repository contains a small dependency-light MCP server for working with Apache Software Foundation Incubator podlings.xml data.
Project Layout
podlings/data.py- XML loading, parsing, normalization, sponsor classification, and date/duration helpers
podlings/tools.py- MCP tool handlers and shared argument/analytics helpers
podlings/schemas.py- Shared tool schema fragments and schema-builder helpers
podlings/protocol.py- JSON-RPC/MCP stdio protocol handling
server.py- Thin entrypoint
tests/- Unit and integration tests
tests/fixtures.py- Shared Python test fixtures and temp XML helpers
tests/fixtures/- File-based test fixtures such as
sample-podlings.xml
- File-based test fixtures such as
Key Defaults And Concepts
sponsor_typedefaults toincubatorfor filtering and analytics tools unless explicitly overridden.completedmeans podlings that reached an end state:graduatedorretired.- Count/rate timeline tools place results into years using
enddate. - Duration timeline tools use both
startdateandenddate.
Developer Workflow
Use these commands before finishing changes:
make check-formatmake lintmake typecheckmake test
CI runs the same checks in GitHub Actions.
Contribution Guidelines
- Keep new MCP tool schema definitions in
podlings/schemas.py. - Keep MCP protocol wiring in
podlings/protocol.py. - Prefer extending shared helpers in
podlings/tools.pyover copying analytics logic. - Add tests for any new tool, filter, or output shape.
- Update
README.mdwhen adding or changing public MCP tools or defaults. - Keep test-only data under
tests/fixtures.pyortests/fixtures/rather than at the repo root.
Testing Notes
- Direct tool behavior belongs in
tests/test_tools.py. - Parsing/data behavior belongs in
tests/test_data.py. - Protocol helper behavior belongs in
tests/test_protocol.py. - End-to-end MCP stdio coverage belongs in
tests/test_mcp_integration.py.
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 · 59 lines · 467 tokens per session scan A 779a1ff03152
PodlingsMCP AGENTS.md is an instructions file published in the GitHub repository justinmclean/PodlingsMCP (0 stars, last pushed 4mo ago), licensed MIT. It adds 467 tokens to every session, about $0.0023 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.