Borrowing it
Nothing to install: this file belongs to felixkwasisarpong/incident-triage-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/felixkwasisarpong/incident-triage-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/felixkwasisarpong/incident-triage-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/felixkwasisarpong/incident-triage-mcp/agents-md)<a href="https://agentmods.dev/instructions/felixkwasisarpong/incident-triage-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/felixkwasisarpong/incident-triage-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/felixkwasisarpong/incident-triage-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/felixkwasisarpong/incident-triage-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.00292 | $0.00292 |
| Opus 5 | $0.00146 | $0.00146 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
incident-triage-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 10d 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
AI-Assisted Contribution Rules
This file defines repository policy for AI-assisted contributions in incident-triage-mcp.
Principles
- Human maintainers are accountable for all merged changes.
- AI can draft code, docs, and tests, but humans review and validate final behavior.
- Keep changes small, traceable, and reproducible.
Required for AI-Assisted PRs
- State where AI was used (drafting, refactoring, tests, docs).
- Add or update tests for behavior changes.
- Update docs for interface or workflow changes.
- Ensure generated code does not introduce secrets or sensitive incident data.
Safety Requirements for Mutating Tools
AI-generated changes must not weaken mutation guardrails. Keep all of the following:
- Safe
dry_runpath confirm_tokenrequirement for non-dry-run execution- Audit logging for mutation attempts
- Idempotency protections where applicable
- RBAC checks for privileged actions
Interface and Spec Stability
- Do not break
EvidenceBundle v1contract shape or semantics. - Do not introduce breaking MCP tool schema changes without a migration plan.
- Prefer implementing provider adapters in Airflow (evidence plane) rather than MCP, unless a direct MCP integration is clearly justified.
Prohibited
- Auto-merging AI-generated output without human review
- Removing guardrails to make demos easier
- Fabricating test results, benchmarks, or incident evidence
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.
- 10d ago First seen · 38 lines · 292 tokens per session scan A b39f1f3e3013
incident-triage-mcp AGENTS.md is an instructions file published in the GitHub repository felixkwasisarpong/incident-triage-mcp (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 292 tokens to every session, about $0.0015 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).
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.
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 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).