Borrowing it
Nothing to install: this file belongs to minghsuy/ctscout-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/minghsuy/ctscout-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/minghsuy/ctscout-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/minghsuy/ctscout-mcp/agents-md)<a href="https://agentmods.dev/instructions/minghsuy/ctscout-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/minghsuy/ctscout-mcp/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.00761 | $0.00761 |
| Opus 5 | $0.00380 | $0.00380 |
| Sonnet 5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
ctscout-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 7d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ctscout-mcp — Agent Guidelines
Pre-Session Checklist
Before starting any task:
- Run
gh pr list --repo minghsuy/ctscout-mcp --state open. For implementation work, stop if a different open PR already touches the planned target files (the files the current task would modify). When reviewing or addressing the current PR, do not treat that PR itself as a collision. - Run
git status --short --branch. If the tree is dirty, do not stash, clean, reset, or overwrite local files; work from an isolated worktree based on the current upstream branch. - Read
README.md,LIMITATIONS.md, andCHANGELOG.mdfor the public package contract relevant to the change.
Verification
Run all of these before pushing:
npm run build
npm run typecheck
npm run lint
npm test
npm audit --audit-level=low
Tests must not depend on a real API key or live ctscout.dev traffic.
For focused iteration, use npx vitest run <path>; still run the full gate
above before pushing.
Repository Boundaries
- This package is the local stdio compatibility client. Hosted Streamable HTTP
and SSE transport implementation belongs in
ctscout-worker. - Keep stdout exclusively for MCP JSON-RPC. Send boot diagnostics and errors to stderr; never log API keys or authorization headers.
- Require Node.js 20 or newer and keep
CTSCOUT_API_KEYin the environment. - Never commit
.env, local MCP client configuration, generated coverage, or editor/agent state.
Code Review Rules
MCP and API contracts
- Treat tool names, descriptions, schemas, normalized responses, errors, quota behavior, and exit behavior as public contracts. Preserve compatibility and add protocol-level tests for any externally observable change.
Cross-repository parity
- When the tool surface changes, explicitly compare it with the hosted MCP
surface in
ctscout-worker. Update both implementations or document and test why a transport-specific difference is intentional; do not claim automatic parity without a check.
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.
- 7d ago First seen · 84 lines · 761 tokens per session scan A 8b287f4058e5
ctscout-mcp AGENTS.md is an instructions file published in the GitHub repository minghsuy/ctscout-mcp (0 stars, last pushed today), licensed MIT. It adds 761 tokens to every session, about $0.0038 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.