Borrowing it
Nothing to install: this file belongs to cybozu/prompt-hardener. 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/cybozu/prompt-hardener/main/AGENTS.mdgit clone --depth 1 https://github.com/cybozu/prompt-hardenerWrote 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/cybozu/prompt-hardener/agents-md)<a href="https://agentmods.dev/instructions/cybozu/prompt-hardener/agents-md"><img src="https://agentmods.dev/badge/instructions/cybozu/prompt-hardener/agents-md.svg" alt="Measured on agentmods" 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.01188 | $0.01188 |
| Opus 5 | $0.00594 | $0.00594 |
| Sonnet 5 | $0.00238 | $0.00238 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
prompt-hardener 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Hardener
Automated evaluation and hardening of LLM system prompts against prompt injection attacks.
Project Overview
Prompt Hardener is an open-source CLI tool that evaluates and strengthens system prompts used in LLM-based applications. It uses a unified agent specification (agent_spec.yaml) to describe the agent under test, then performs layered security analysis, iterative remediation, and attack simulation.
Supported Agent Types
| Type | Description | Analyzed Layers |
|---|---|---|
chatbot |
Simple conversational bots | prompt |
rag |
Retrieval-augmented generation systems | prompt, architecture |
agent |
Tool-calling agents | prompt, tool, architecture |
mcp-agent |
MCP server-connected agents | prompt, tool, architecture |
Core Workflow
init -> validate -> analyze -> remediate -> simulate -> report -> diff
- init - Generate an
agent_spec.yamlfrom a template - validate - Schema + semantic validation of the spec
- analyze - Static rule-based analysis + optional LLM evaluation
- remediate - Three-layer remediation (prompt / tool / architecture)
- simulate - Run attack scenarios from the built-in catalog
- report - Generate formatted reports from JSON results
- diff - Compare before/after specs
Architecture
agent_spec.yaml
|
v
[validate] --> schema + semantic checks
|
v
[analyze] --> rules engine (per layer) + optional LLM evaluation
| |
| v
| AnalyzeReport (findings, scores, attack paths)
v
[remediate] --> prompt_layer (LLM iterative improvement)
| tool_layer (tool config recommendations)
| arch_layer (architecture recommendations)
| |
| v
| RemediationReport + updated agent_spec.yaml
v
[simulate] --> catalog scenarios -> attack execution -> judge
| |
| v
| SimulationReport (blocked/succeeded per scenario)
v
[report] --> markdown / HTML / JSON output
[diff] --> before/after comparison
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.
- 7d ago First seen · 155 lines · 1,188 tokens per session scan A 7bbe978d8c94
prompt-hardener AGENTS.md is an instructions file published in the GitHub repository cybozu/prompt-hardener (54 stars, last pushed 6d ago), licensed Apache-2.0. It adds 1,188 tokens to every session, about $0.0059 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-30.
Other instructions, from other repositories
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).
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.
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).
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.