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/ondata/ckan-mcp-server/agents-mdgit clone --depth 1 https://github.com/ondata/ckan-mcp-serverWrote 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/ondata/ckan-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/ondata/ckan-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/ondata/ckan-mcp-server/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.1 | $0.01487 | $0.01487 |
| Opus 5 | $0.00744 | $0.00744 |
| Sonnet 5 | $0.00297 | $0.00297 |
| Haiku 4.5 | $0.00149 | $0.00149 |
Grade A, and why
ckan-mcp-server AGENTS.md 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 6d 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 -s -X POST http://localhost:3001/mcp \ How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Instructions
These instructions are for AI assistants working in this project.
Always open @/openspec/AGENTS.md when the request:
- Mentions planning or proposals (words like proposal, spec, change, plan)
- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work
- Sounds ambiguous and you need the authoritative spec before coding
Use @/openspec/AGENTS.md to learn:
- How to create and apply change proposals
- Spec format and conventions
- Project structure and guidelines
Keep this managed block so 'openspec update' can refresh the instructions.
Agent Guide
Scope
- Repo:
ckan-mcp-server - Stack: Node.js + TypeScript (ESM)
- Tests: Vitest
- Build: esbuild
- Cloudflare Workers:
wrangler
Cursor and Copilot Rules
- No
.cursor/rules,.cursorrules, or.github/copilot-instructions.mdfound
Commands
Install: npm install
Build: npm run build | npm run build:tsc | npm run build:worker
Run: npm start | npm run dev | npm run watch | npm run dev:worker | npm run deploy
Test: npm test | npm run test:watch | npm run test:coverage
Single test: npm test -- tests/unit/http.test.ts | npm test -- -t "testName"
Local MCP Client Build Test
Before deploying, you can test the current dev build by pointing your MCP client at the Node entrypoint in dist/:
- Build:
npm run build - Example absolute path:
/home/aborruso/git/idee/ckan-mcp-server/dist/index.js(adjust to your local checkout)
GitHub CLI Notes
When creating issues with multi-line bodies, avoid literal \n in --body. Use a here-doc
or -F - to preserve newlines:
cat <<'EOF' | gh issue create --title "Title" --body-file - --repo ondata/ckan-mcp-server
Line 1
Line 2
EOF
When writing GitHub release notes, avoid literal \n in --notes. Always pass a here-doc
via --notes-file - so line breaks render correctly:
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.
- 6d ago First seen · 179 lines · 1,487 tokens per session scan A 26d94c8ec8d6
ckan-mcp-server AGENTS.md is an instructions file published in the GitHub repository ondata/ckan-mcp-server (57 stars, last pushed yesterday), licensed MIT. It adds 1,487 tokens to every session, about $0.0074 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-30.
Other instructions, from other repositories
civic-ai-tools AGENTS.md
AGENTS.md instructions for npstorey/civic-ai-tools, covering agents.md, boundaries, commands, mcp configuration and where the detail lives.
access-to CLAUDE.md
Claude Code instructions for dougdevitre/access-to, covering claude.md — instructions for claude code, project overview, repository structure, commands and validate config files.
access-to copilot-instructions.md
Copilot instructions for dougdevitre/access-to, covering copilot instructions for access to, architecture, key conventions, file structure and code style.
civic-ai-tools CLAUDE.md
Claude Code instructions for npstorey/civic-ai-tools, a project described as: Open-source platform connecting AI assistants to government open data — MCP server, curated civic MCP directory, and anti-hallucination framework for all 559 Socrata portals.
uk-parliament-data-mcp CLAUDE.md
Instructions for ChrisBrooksbank/uk-parliament-data-mcp, covering claude.md, project overview, installation, from pypi (recommended) and or run without installing.
uk-parliament-data-mcp AGENTS.md
Instructions for ChrisBrooksbank/uk-parliament-data-mcp, covering agents.md - operational guide, build commands, install dependencies (dev mode), run the mcp server and test commands.