agentleFS
c-monganc-mongan/ireland-mcp/AGENTS.md

ireland-mcp

AGENTS.md2 starsChanged 19 days agoMITView on GitHub

Ireland MCP is a read-only Model Context Protocol server for Irish public data. See CONTRIBUTING.md for the full contributor guide. Node 22.12 or later. npm run live:sanity and npm run live:all call real upstream services. Run them by hand; they are not part of PR CI (the nightly live-smoke workflow runs live:sanity). - Tools are read-only, named {source}_{verb}, and return an evidence envelope with source, URL, licence, attribution and retrieval time. - Bound every list and throw ToolError with a…

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 1 is common, 4 are distinctive, and 1 is very specific to this project.

  • ≈1

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Write the failing test first for new behaviour.

    line 41
  2. Distinctive:

    Do not claim live coverage, deployment or passing checks without evidence.

    line 43
  3. Common:

    Never commit secrets, tokens, subscription IDs or personal paths.

    line 44
  4. Distinctive:

    If a check cannot run locally (missing dependency, restricted sockets), say so rather than skipping it silently.

    line 45
  5. Distinctive:

    Use fixed official URLs, bounded reads and explicit response validation.

    line 53
  6. Very specific:

    Add a bounded case to scripts/live-sanity.mjs (environment-gated if it needs an operator key).

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Guidance for contributors and coding agents

Ireland MCP is a read-only Model Context Protocol server for Irish public data. See CONTRIBUTING.md for the full contributor guide.

Commands

Node 22.12 or later.

npm ci
npm run typecheck
npm run lint
npm test                 # unit tests replay fixtures, no network
npm run build
npm run inspector:check  # MCP conformance via the Inspector CLI (after build)
npm run dev:http         # local server on http://localhost:7071
npm run legal:check      # legal corpus package checks

npm run live:sanity and npm run live:all call real upstream services. Run them by hand; they are not part of PR CI (the nightly live-smoke workflow runs live:sanity).

Layout

  • src/gateway/: envelope, errors, caching and tool definition helpers
  • src/sources/<id>/: one module per upstream source, with fixtures and tests
  • src/registry.ts: registers source modules
  • packages/irish-legal-mcp/: optional legal and Citizens Information pilot corpus
  • web/: static site; storybook/: component previews
  • skills/: packaged user-facing skills; infra/: Azure infrastructure as code
  • docs/: deployment, operations and evidence notes

Conventions

  • Tools are read-only, named {source}_{verb}, and return an evidence envelope with source, URL, licence, attribution and retrieval time.
  • Bound every list and throw ToolError with a hint. Never build an upstream URL from a user-supplied host.
  • Write the failing test first for new behaviour.
  • Preserve source attribution and legal-currentness warnings.
  • Do not claim live coverage, deployment or passing checks without evidence.
  • Never commit secrets, tokens, subscription IDs or personal paths.
  • If a check cannot run locally (missing dependency, restricted sockets), say so rather than skipping it silently.

CI enables LEGAL_SOCKET_TESTS=1 and runs lint, typecheck, tests, the build and the Inspector conformance check.

Reviewing a new source

  • Use fixed official URLs, bounded reads and explicit response validation. An empty or malformed response must not become valid zero data or enter the cache.
  • Preserve publisher attribution, reporting dates, retrieval dates, missing values, stale state and transfer-limit flags. A local or fixture check is not hosted verification.
  • Add a bounded case to scripts/live-sanity.mjs (environment-gated if it needs an operator key).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.