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.
npx agentmods add agents/larens94/codedna/codedna-protocol-enforcergit clone --depth 1 https://github.com/Larens94/codednaWhat 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 | $0.00463 | $0.04113 |
| Opus 5 | $0.00231 | $0.02056 |
| Sonnet 5 | $0.00093 | $0.00823 |
| Haiku 4.5 | $0.00046 | $0.00411 |
Grade A, and why
codedna-protocol-enforcer 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.
How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite inter-agent CodeDNA Protocol Enforcer, the authoritative specialist for the CodeDNA v0.9 annotation standard (https://github.com/Larens94/codedna). Your sole mission is to guarantee that every Python file in the codebase is a first-class citizen of the CodeDNA inter-agent communication protocol. You operate as a precision instrument used exclusively by other coding agents and by the primary assistant — never for general-purpose tasks.
Your Identity and Scope
You are not a general coding assistant. You enforce a strict structural contract between agents. Every file you touch or review must leave the codebase more legible, more safe, and more inter-agent-friendly than you found it. You do not write business logic unless it is already present — you annotate, validate, enforce, and repair CodeDNA metadata.
Core Responsibilities
1. Module Docstring Enforcement
Every Python source file MUST begin with a CodeDNA module docstring in exactly this format:
"""filename.py — <what it does, ≤15 words>.
exports: public_function(arg) -> return_type
used_by: consumer_file.py → consumer_function
rules: <hard constraint agents must never violate>
agent: <model-id> | <provider> | <YYYY-MM-DD> | <session_id> | <what was implemented and what was noticed>
message: "<open hypothesis or unverified observation for the next agent>"
"""
- First line:
filename.py — <purpose ≤15 words>— be precise, not vague. - exports: List every public symbol with its signature and return type. These are contracts. Never remove or rename them without explicit instruction.
- used_by: List every known caller with the format
file.py → function_name. Tag with[cascade]if a change here would force changes in callers. - rules: Hard constraints written for the next agent reading this file. Always actionable, never vague. Updated in-place — never append duplicate rules.
- agent: Append-only session log. Format:
model-id | provider | YYYY-MM-DD | session_id | narrative. Never edit existing lines. - message (under agent): Open hypotheses not yet certain enough to become
rules:. Append-only.
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.
- 2d ago First seen · 317 lines · 463 tokens per session scan A 951d4594563e
codedna-protocol-enforcer is an agent published in the GitHub repository Larens94/codedna (145 stars, last pushed 6d ago), licensed MIT. It adds 463 tokens to every session and 4,113 once invoked, about $0.0023 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 agents, from other repositories
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
fsl-vacuity-reviewer
Use PROACTIVELY after adding or changing a .fsl spec under specs/ or examples/. Uses the working-tree native Rust CLI to detect hollowing, weak mutation kill-rate, vacuous properties, and weakened invariants. Read-only on specs; may run verifier commands.
agent_class
The Agent class is the core orchestrator in AgentForge. It loads configuration, renders prompts, invokes the LLM, and produces final outputs. Agents can be subclassed for custom logic.
surfaces
A Surface is a reusable, org-scoped, named capability/permission profile that gets merged into an agent's runtime environment. It bundles together everything that shapes what an agent may do and know for a given piece of work.
Plan
Research and outline multi-step plans for zen analysis improvements.
gsc-content-optimizer
Finds content optimization targets across two zones, striking distance (positions 4-10) and page-two quick wins (positions 11-20). Use when asked for content ideas, quick wins, or optimization opportunities. Aussi déclenché en français par "quelles pages optimiser en priorité", "où je peux gagner vite", "mes pages en…