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 skills/arch1esun/arcgentic/codify-lessonnpx skills add Arch1eSUN/Arcgentic --skill codify-lessongit clone --depth 1 https://github.com/Arch1eSUN/ArcgenticWrote 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/skills/arch1esun/arcgentic/codify-lesson)<a href="https://agentmods.dev/skills/arch1esun/arcgentic/codify-lesson"><img src="https://agentmods.dev/badge/skills/arch1esun/arcgentic/codify-lesson.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 | $0.00033 | $0.00367 |
| Opus 5 | $0.00016 | $0.00183 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
codify-lesson 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 4d 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.
What it actually says
codify-lesson
Scans recent audit handoffs for recurring P2/P3 patterns in structured findings tables and promotes repeated clusters into lesson cards.
When to invoke
- After
round-boundary-lesson-scanreports a promotable cluster - User invokes
/codify-lesson - 3+ rounds show the same structured finding pattern
Workflow
-
Shell out to the toolkit:
arcgentic codify-lesson \ --audit-dir docs/audits \ --lessons-dir lessons \ --amendments-dir mandates/amendments -
Read stdout:
lessons: Namendments: Nstreak_updates: N
-
Inspect every generated lesson card before accepting it.
-
If an amendment proposal is generated, stop for founder review before applying mandate/rule changes.
The scanner ignores reference scans, author notes, forward-debt prose, and other
unstructured markdown even when those sections mention P2 or P3.
Output contract
- New lesson card:
lessons/lesson-{N}-{slug}.md - Formal-threshold amendment proposal:
mandates/amendments/amendment-{slug}.md - Existing lesson streak updates when a lesson was preserved
See also
agents/lesson-codifier.mdtoolkit/src/arcgentic/skills_impl/codify_lesson.pytoolkit/src/arcgentic/utils/pattern_detection.py
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.
- 4d ago First seen · 52 lines · 33 tokens per session scan A 77882143180e
codify-lesson is a skill published in the GitHub repository Arch1eSUN/Arcgentic (292 stars, last pushed 22d ago), licensed MIT. It adds 33 tokens to every session and 367 once invoked, about $0.0002 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 skills, from other repositories
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
init
Write or refresh the ## Tech debt operations section in CLAUDE.md so a team shares one source of truth for debt-ops disciplines and cached quality commands. Idempotent. Only the managed section changes; other sections are untouched. Invoked explicitly via /debt-ops:init (solo users get the same content from the…
review
Audit the debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or invokes /debt-ops:review. Stale entries drop with drop A,B,C.
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.
add
Register a deferred decision in the debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you defer…
metrics
Print a debt-ops health summary from the metrics log, covering registration rate, hook feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or invokes /debt-ops:metrics. Read-only, never writes the log.