Borrowing it
Nothing to install: this file belongs to cristianoaredes/mcp-senado. 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/cristianoaredes/mcp-senado/master/AGENTS.mdgit clone --depth 1 https://github.com/cristianoaredes/mcp-senadoWrote 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/cristianoaredes/mcp-senado/agents-md)<a href="https://agentmods.dev/instructions/cristianoaredes/mcp-senado/agents-md"><img src="https://agentmods.dev/badge/instructions/cristianoaredes/mcp-senado/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.00651 | $0.00651 |
| Opus 5 | $0.00326 | $0.00326 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
mcp-senado 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 8d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
TypeScript source lives in lib/: core/ owns the MCP server and tool registry, tools/ exposes Senado commands, infrastructure/ handles cache, HTTP, and resilience helpers, and bin/ contains the runnable entries that compile to build/bin/. Shared schemas sit in lib/types/, while Worker glue code is in lib/workers/. Tests mirror runtime folders under test/ (core, integration, e2e, infrastructure).
Build, Test, and Development Commands
npm run dev– watcheslib/bin/mcp-senado.tswithtsxfor local TCP development.npm run dev:http– launches the Express transport for REST-based testing.npm run build– compiles strict ESM output and declarations intobuild/.npm run test/npm run test:watch– runs Vitest across all suites once or continuously.npm run test:coverage– captures V8 coverage; keep the number close to the published ~73%.npm run lint– performs type-level linting viatsc --noEmit.npm run smoke– executesscripts/smoke-test.tsto validate Senado API connectivity.
Coding Style & Naming Conventions
Stick to ES modules, 2-space indentation, and explicit return types. Favor named exports and directory index.ts barrels, as shown in lib/index.ts. Files stay kebab-case (senators-tool.ts); exported classes, schemas, and Zod objects use PascalCase, helpers use camelCase. Keep error messages actionable and run npm run lint before committing because no formatter runs in CI.
Testing Guidelines
Add unit specs beside the closest runtime analog within test/<area>, using .spec.ts or .test.ts suffixes tied to the tool name (proposals.spec.ts). Mock Senado responses with the shared fixtures/utilities in test. Vitest reads from vitest.config.ts; update integration or e2e suites whenever new endpoints or resilience layers ship. Maintain baseline coverage locally with npm run test:coverage before opening a PR.
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.
- 8d ago First seen · 26 lines · 651 tokens per session scan A 5a7bd4e7bd4b
mcp-senado AGENTS.md is an instructions file published in the GitHub repository cristianoaredes/mcp-senado (6 stars, last pushed 5mo ago), licensed MIT. It adds 651 tokens to every session, about $0.0033 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
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.
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.
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).
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).
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.
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.