Borrowing it
Nothing to install: this file belongs to jdlar1/siigo-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jdlar1/siigo-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/jdlar1/siigo-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/jdlar1/siigo-mcp/agents-md)<a href="https://agentmods.dev/instructions/jdlar1/siigo-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jdlar1/siigo-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/jdlar1/siigo-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jdlar1/siigo-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00245 | $0.00245 |
| Opus 5.5 | $0.00098 | $0.00098 |
| Sonnet 5.5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
siigo-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 1mo 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
Working agreements
- Make the smallest change that fully addresses the task. Reuse existing patterns before introducing abstractions or tooling.
- Preserve public contracts unless the requested task authorizes a breaking change. Document intentional migrations and their compatibility path.
- Design MCP tools around user tasks. An API endpoint does not automatically need a public tool; preserve API coverage through the client and discoverable operations.
- Keep reads, writes, and destructive actions distinguishable. Never resolve an ambiguous accounting reference by silently choosing a match.
- Preserve upstream error context, cancellation, and idempotency when composing operations. Do not silently swallow failures or retry non-idempotent writes.
- Verify observable behavior with mocked upstream calls. Do not use live accounting data or create real documents to run tests.
- Read the current package scripts, configuration, and implementation before making assumptions about commands, versions, file locations, or architecture.
- Run checks appropriate to the change and report any unverified behavior.
- Keep this file limited to working agreements. Versions, commands, formatting, file inventories, and implementation details belong in their existing sources of truth, not in a second copy here.
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.
- 1mo ago Changed · -149 lines · -1,623 tokens per session 71f0e618c937
- 2mo ago First seen · 170 lines · 1,868 tokens per session scan A 43f4e9942daa
siigo-mcp AGENTS.md is an instructions file published in the GitHub repository jdlar1/siigo-mcp (9 stars, last pushed 11d ago), licensed MIT. It adds 245 tokens to every session, about $0.0010 per session on Opus 5.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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
generative-ai-for-beginners AGENTS.md
AGENTS.md instructions for microsoft/generative-ai-for-beginners, covering agents.md, project overview, setup commands, initial repository setup and clone the repository.