agentmods.dev

penthera: Instructions file for Codex

AGENTS.md

penthera AGENTS.md is an instructions file for Codex, OpenCode from danoszz/penthera. It costs 851 tokens per session, scanned A, original, MIT.

A project guide for Penthera, an offline security agent for Node.js. It explains the repository layout, commands, rules, and requirements for working on the project.

In plain words
What is it for?
Use it when developing, testing, linting, auditing, or understanding the Penthera codebase.
Why use it?
It gives a coding agent the project-specific instructions needed to avoid breaking tests, documentation checks, release checks, or offline behavior.

Instructions file for CodexOpenCode

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

This is danoszz/penthera's own configuration. It tells Codex and OpenCode how to work on penthera 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 penthera configures →

not rated 71repo +22 changed yesterday A scan 851 tokens original MIT
View source ↗ danoszz/penthera penthera.org
Reuse

Borrowing it

Nothing to install: this file belongs to danoszz/penthera. 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/danoszz/penthera/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/danoszz/penthera

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 penthera AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/danoszz/penthera/agents-md"><img src="https://agentmods.dev/badge/instructions/danoszz/penthera/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 851 This file is loaded in full into every session.
When invoked 851 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.00851 $0.00851
Opus 5.5 $0.00340 $0.00340
Sonnet 5.5 $0.00170 $0.00170
Haiku 4.5 $0.00085 $0.00085

Measured yesterday against content hash 5b8d3c55680d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

penthera 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 yesterday.

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 · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Project page. For coding agents asking "how do I work on Penthera, or use it, without breaking its rules?"

Penthera is an offline, rule-based security agent (MIT, Node.js 22 or later). Deterministic rules decide every finding. A model may only propose.

Commands

Command What it does
npm install Install dependencies
npm test The full suite (vitest), including docs-as-tests and the changelog check
npm run lint ESLint: unused code, undefined names, unreachable code
npm run audit:internal The release gate, written to audit/REPORT.md; includes the docs link check
npm run changelog Checks every fragment in changelog.d/

Tests must stay offline and parallel-safe: temp dirs, port 0, no real HOME. The details are in CONTRIBUTING.md.

Layout

bin/          CLI entry points
src/          CLI and orchestration: scan-url, scan-repo, reporter, ui, mcp, agent loop
lib/          the engine: blackbox, whitebox, deps, agents, install, hook, fix,
              advisories, rules, ai, memory, compliance
skills/       the Agent Skill (skills/penthera/SKILL.md)
tests/        vitest suites and fixtures
bench/        the benchmark and the E10 known-vulnerable-apps runner
docs/         user docs (start at docs/index.md); docs/research/ holds research notes
changelog.d/  one changelog fragment per pull request
site/         penthera.org

Rules

  1. Add a changelog fragment in changelog.d/ with a section: line (format). Do not edit CHANGELOG.md.

  2. Add the trailers to every commit you write. CI rejects a commit that has one without the other (scripts/ci/provenance.mjs):

    AI-Assisted: <tool> with <model and version>; <what it did, in one line>
Co-Authored-By: <model and version> <vendor noreply address>

  3. No version bumps or tags. Only the maintainer starts a release.

  4. Rules decide. Do not add a code path where a model's output becomes a finding, a fix or an exit code without a deterministic check.

  5. No run-time downloads of rules, templates or signatures. Rules ship in releases.

  6. Only authorized targets. Scan your own code, loopback, or hosts the maintainer named. Never point a scan or a test at a third-party system.

  7. Docs follow the voice guide. Every command you document must exist in --help; npm test checks it.

Read the full file on GitHub · 72 lines

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. yesterday Changed · +3 tokens per session 5b8d3c55680d
  2. 3d ago Changed · -1 lines · -31 tokens per session 7c962081bc59
  3. 4d ago First seen · 73 lines · 879 tokens per session scan A 71f839e555e9

Subscribe to this mod's changes

penthera AGENTS.md is an instructions file published in the GitHub repository danoszz/penthera (71 stars, last pushed yesterday), licensed MIT. It adds 851 tokens to every session, about $0.0034 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-10-23.

Claude CodeSecurityagent-skillsclicursorowasppentest
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 · 9,715 tokens

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.

vercel/next.js · 7,786 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens