secscan_mcp AGENTS.md

Repository instructions for secscan-mcp, a Python server that scans code for secrets, code flaws, vulnerable dependencies, and infrastructure settings.

In plain words
What is it for?
Use them when developing, testing, releasing, or contributing changes to secscan-mcp.
Why use it?
They explain the project structure, required checks, release process, and rules for handling commits and secrets.

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/openjkai/secscan_mcp/agents-md
Clone the repo
git clone --depth 1 https://github.com/openjkai/secscan_mcp

Made for: Codex, OpenCode.

Per session 318 This file is loaded in full into every session.
When invoked 318 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.00318 $0.00318
Opus 5 $0.00159 $0.00159
Sonnet 5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

secscan_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 2d 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 · 25 lines

What it actually says

Agent guide (secscan-mcp)

Project

Python MCP server wrapping security scanners (gitleaks, semgrep, osv-scanner, etc.). Full design: PLAN.md.

Conventions

  • Package: src/secscan_mcp/
  • Run make check before finishing a change
  • Use Ruff for format/lint; mypy strict on src/
  • Minimize scope; one concern per commit when the user asks for commits

Git

  • Do not commit unless the user explicitly requests it
  • Never commit secrets, .env, or .scan-output/
  • Follow .cursor/rules/git-commits.mdc and git-workflow.mdc

Current phase

Phase 4 — Community & discovery. v0.3.0 is on PyPI: finding suppression via .secscanignore (path globs) + inline # nosecscan comments, applied across all engines with a suppressed count in every report. Prior: scan_all + git history, engine-aware explain_finding, SECURITY.md. Next: issue templates, MCP registry submissions. Release via make release-patch|minor PYTHON=python3.11 — see docs/PUBLISHING.md.

Suppression lives in src/secscan_mcp/suppress.py and is applied in normalize.build_report — every engine benefits, nothing engine-specific.

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. 2d ago First seen · 25 lines · 318 tokens per session scan A 5077e8b55e7c

Subscribe to this mod's changes

secscan_mcp AGENTS.md is an instructions file published in the GitHub repository openjkai/secscan_mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 318 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.

Related

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).

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens