scan-mcp AGENTS.md

Project instructions for developing scan-mcp, including its build, testing, style, release, and pull-request practices.

In plain words
What is it for?
Use them when installing dependencies, linting, type-checking, testing, building, verifying, preparing commits, or handling automated releases for scan-mcp.
Why use it?
They give an agent the repository's expected commands and conventions, reducing inconsistent changes and missed verification steps.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/jacksenechal/scan-mcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/jacksenechal/scan-mcp

Made for: Codex, OpenCode.

Per session 327 This file is loaded in full into every session.
When invoked 327 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00327 $0.00327
Opus 5 $0.00163 $0.00163
Sonnet 5 $0.00065 $0.00065
Haiku 4.5 $0.00033 $0.00033

Measured 3d ago against content hash 9c76cf5c6a33, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scan-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 3d 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.

AGENTS.md · 29 lines

What it actually says

Agent Guidelines

Build, Test, and Development Commands

  • Run commands from this directory.
  • make install installs dependencies.
  • make lint, make typecheck, make test, make build, and make verify mirror package.json scripts.
  • npm test runs the Vitest suite.

Code & Project Conventions

  • See CONVENTIONS.md for coding style, project structure, security, and testing guidelines.

Commit & Pull Request Guidelines

  • Use conventional commit prefixes when practical (feat:, fix:, docs:, etc.).
  • Keep commits focused and run make verify before sending a PR.
  • PRs should include a concise summary and relevant command output.

Releases (release-please)

  • This repo uses release-please to automate versioning and changelog generation.
  • Do not manually bump versions in package.json or other manifests.
  • Use conventional commits; release-please derives the next version from commit history.
  • If you need to force a specific version for a PR, include a line in the merge (squash) commit message body:
    • Release-As: x.y.z
  • CI will open or update a release PR; merging it publishes the release per the configured workflow.

Network and Approvals Policy

  • Network access is allowed for installing packages, fetching docs, or calling external APIs.
  • If the sandbox blocks a command, re-run it with elevated permissions and a brief justification.
  • Do not commit secrets; document required environment variables instead.
Changes

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.

  1. 3d ago First seen · 29 lines · 327 tokens per session scan A 9c76cf5c6a33

Subscribe to this mod's changes

scan-mcp AGENTS.md is an instructions file published in the GitHub repository jacksenechal/scan-mcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 327 tokens to every session, about $0.0016 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.