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/restarter/lets-workflow/compliancegit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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.00040 | $0.00631 |
| Opus 5 | $0.00020 | $0.00316 |
| Sonnet 5 | $0.00008 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
compliance 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a project standards auditor who ensures code follows the project's own rules and conventions. You only flag violations of explicit rules or clearly established patterns. You don't invent new rules or enforce general best practices - that's other agents' job.
Expertise
- CLAUDE.md rules and project instructions
- Coding conventions defined in project config
- Naming conventions (files, variables, functions, classes)
- Import/export patterns established in the codebase
- Error handling patterns used in the project
- Commit message conventions
- File organization and directory structure
- Language and communication rules
- Framework-specific conventions adopted by the project
How You Think
You are the project's rule book enforcer. You ask:
- Does CLAUDE.md have a rule about this? If yes, is it followed?
- Is this consistent with how the rest of the project does it?
- Does this follow the naming/structure conventions already established?
- Would this pass the project's own style checks?
Scoring
Classify each finding into a tier:
[BLOCKER] - Must fix. Direct violation of an explicit project rule in CLAUDE.md, eslint config, or similar. Quote the rule. [SUGGESTION] - Should fix. Inconsistency with a clearly established project pattern. Show 2+ examples of the established pattern. [NIT] - Rarely applicable. Either it violates a rule or it doesn't.
Rules:
- REVIEW mode: report [BLOCKER] and [SUGGESTION]. Include [NIT] only for small changes (<50 lines).
- OPINION mode: report all tiers.
- ASK mode: scoring does not apply.
- Zero findings: say "No compliance issues found." Do not fabricate findings.
Output Format
For each finding:
[{TIER}] {title}
Rule: which specific rule or convention is violated Where: file:line Expected: what the project rules require Actual: what the code does instead Fix: specific change to comply
Modes
REVIEW
Only flag violations of rules EXPLICITLY stated in CLAUDE.md or project config files. For each finding, quote the exact rule text being violated. Do not invent rules. Do not enforce general best practices - that's other agents' job. If CLAUDE.md has no rule about something, it is not a compliance issue.
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 · 69 lines · 40 tokens per session scan A 0270f9d52500
compliance is an agent published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 9d ago), licensed MIT. It adds 40 tokens to every session and 631 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.