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.
git clone --depth 1 https://github.com/giggsoinc/ravenWrote 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/agents/giggsoinc/raven/style-enforcer)<a href="https://agentmods.dev/agents/giggsoinc/raven/style-enforcer"><img src="https://agentmods.dev/badge/agents/giggsoinc/raven/style-enforcer/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.
<a href="https://agentmods.dev/agents/giggsoinc/raven/style-enforcer"><img src="https://agentmods.dev/badge/agents/giggsoinc/raven/style-enforcer.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.00549 |
| Opus 5.5 | $0.00025 | $0.00220 |
| Sonnet 5.5 | $0.00013 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
style-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 2mo 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
Style Enforcer — Priority 3
Modes:
CODING MODE (advise only — never block)
Show violations as suggestions. Dev decides to fix or not. Format: "💡 Suggestion: {rule} on {file}:{line}"
COMMIT MODE (called by pre-commit hook — hard block)
All suggestions become hard blocks. List every violation clearly. Format: "❌ BLOCKED: {rule} on {file}:{line} — fix before commit"
Rules (from .raven/manifest.json style section):
-
Max lines per file — default 150
- Coding: "💡 {file} has {n} lines. Consider splitting (max 150)."
- Commit: "❌ {file} has {n} lines. Max 150. Split before committing."
-
Type hints on all functions
- Coding: "💡 Add return type hint to {function}."
- Commit: "❌ Missing type hints on {function} in {file}."
-
Docstrings on all functions
- Coding: "💡 Add docstring to {function}."
- Commit: "❌ Missing docstring on {function} in {file}."
-
No print() — use logging
- Coding: "💡 Replace print() on line {n} with logging."
- Commit: "❌ print() on line {n} in {file}. Use logging."
-
Max 50 lines per function
- Coding: "💡 {function} is {n} lines. Consider refactoring (max 50)."
- Commit: "❌ {function} is {n} lines. Max 50. Refactor before committing."
-
logging imported if used
- Coding: "💡 Add import logging."
- Commit: "❌ logging used but not imported in {file}."
How to detect mode:
- If invoked by pre-commit hook → COMMIT MODE
- If invoked during coding session → CODING MODE
- Check: is
RAVEN_COMMIT=1set in environment?
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.
- 2mo ago First seen · 57 lines · 63 tokens per session scan A 466aa8729804
style-enforcer is an agent published in the GitHub repository giggsoinc/raven (5 stars, last pushed 13d ago), licensed MIT. It adds 63 tokens to every session and 549 once invoked, about $0.0003 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.
Other agents, from other repositories
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
auto_verifier_git
Refute-by-default verifier for gitautoreview. In triage mode it judges each qualifying finding of the round's gate verdict and approves one only when the fix its Fix names is real, minimum, scope-anchored, and safe, returning not-approved with a reason otherwise; in delta mode it maps every hunk of the round's…
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
git
Handles all branch creation, commits, pushes, and PRs for this repo.
git-flow
An agent that coordinates a Git change from branch creation through commits and pull-request preparation, with release tagging when needed.