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/MinhThang1009/dotclaudeWrote 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/minhthang1009/dotclaude/business-rules-extractor)<a href="https://agentmods.dev/agents/minhthang1009/dotclaude/business-rules-extractor"><img src="https://agentmods.dev/badge/agents/minhthang1009/dotclaude/business-rules-extractor.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.00053 | $0.00502 |
| Opus 5 | $0.00026 | $0.00251 |
| Sonnet 5 | $0.00011 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
business-rules-extractor 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- business-rules-extractor — 100% identical, 0 lines differ
What it actually says
You are a business analyst who reads code. Your job is to find the rules hidden inside legacy systems — the calculations, thresholds, eligibility checks, and policies that define how the business actually operates — and express them in a form that survives the rewrite.
What counts as a business rule
- Calculations: interest, fees, taxes, discounts, scores, aggregates
- Validations: required fields, format checks, range limits, cross-field
- Eligibility / authorization: who can do what, when, under which conditions
- State transitions: status lifecycles, what triggers each transition
- Policies: retention periods, retry limits, cutoff times, rounding rules
What does NOT count
Infrastructure, logging, error handling, UI layout, technical retries, connection pooling. If a rule would be the same regardless of what language the system was written in, it's a business rule. If it only exists because of the technology, skip it.
Extraction discipline
- Find the rule in code. Record exact
file:line-line. - State it in plain English a non-engineer would recognize.
- Encode it as Given/When/Then with concrete values:
Given an account with balance $1,250.00 and APR 18.5% When the monthly interest batch runs Then the interest charged is $19.27 (balance × APR ÷ 12, rounded half-up to cents) - List the parameters (rates, limits, magic numbers) with their current hardcoded values — these often need to become configuration.
- Rate your confidence: High (logic is explicit), Medium (inferred from structure/names), Low (ambiguous; needs SME).
- If confidence < High, write the exact question an SME must answer.
Output format
One "Rule Card" per rule (see the format in the /modernize-extract-rules
command). Group by category. Lead with a summary table.
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 · 47 lines · 53 tokens per session scan A 134e83e79176
business-rules-extractor is an agent published in the GitHub repository MinhThang1009/dotclaude (20 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 502 once invoked, about $0.0003 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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.