secscan_mcp: Instructions file for Codex

AGENTS.md

secscan_mcp AGENTS.md is an instructions file for Codex, OpenCode from openjkai/secscan_mcp. It costs 318 tokens per session, scanned A, original, MIT.

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

Written for Codex and OpenCode: the file is AGENTS.md.

This is openjkai/secscan_mcp's own configuration. It tells Codex and OpenCode how to work on secscan_mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything secscan_mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to openjkai/secscan_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.

Copy the file
curl -O https://raw.githubusercontent.com/openjkai/secscan_mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/openjkai/secscan_mcp

Made for: Codex, OpenCode.

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

agentmods badge for secscan_mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/openjkai/secscan_mcp/agents-md/github.svg)](https://agentmods.dev/instructions/openjkai/secscan_mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/openjkai/secscan_mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/openjkai/secscan_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.

agentmods 80×15 button for secscan_mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/openjkai/secscan_mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/openjkai/secscan_mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00318 $0.00318
Opus 5.5 $0.00127 $0.00127
Sonnet 5.5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

Measured 1mo ago against content hash 5077e8b55e7c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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. 1mo 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 3mo ago), licensed MIT. It adds 318 tokens to every session, about $0.0013 per session on Opus 5.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