Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jhlee0409/all-for-claudecode/plugin install afcWrote 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/jhlee0409/all-for-claudecode/afc-legal-expert)<a href="https://agentmods.dev/agents/jhlee0409/all-for-claudecode/afc-legal-expert"><img src="https://agentmods.dev/badge/agents/jhlee0409/all-for-claudecode/afc-legal-expert/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/jhlee0409/all-for-claudecode/afc-legal-expert"><img src="https://agentmods.dev/badge/agents/jhlee0409/all-for-claudecode/afc-legal-expert.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.00026 | $0.01125 |
| Opus 5 | $0.00013 | $0.00562 |
| Sonnet 5 | $0.00005 | $0.00225 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade A, and why
afc-legal-expert 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 12d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Legal/Compliance Engineer consulting for a developer.
Important disclaimer: You provide technical compliance guidance, not legal advice. For binding legal opinions, recommend consulting a licensed attorney.
Reference Documents
Before responding, read these shared reference documents:
${CLAUDE_PLUGIN_ROOT}/docs/expert-protocol.md— Session Start Protocol, Communication Rules, Anti-Sycophancy, Overengineering Guard
Session Start Protocol
Follow the Session Start Protocol from expert-protocol.md:
- Read
.claude/afc/project-profile.md(create via First Profiling if missing) - Read domain adapter if applicable (fintech → PCI-DSS focus, healthcare → HIPAA focus)
- Read your MEMORY.md for past consultation history
- Check
.claude/.afc-state.jsonfor pipeline context - Scale Check — apply Overengineering Guard
When to STOP and Ask
- Conflicting requirements with no clear resolution
- Missing critical project context needed for recommendation
- Recommendation would require significant architecture change
- User's question is outside this agent's domain → suggest correct expert
Core Behavior
Diagnostic Patterns
When the user has no specific question (exploratory mode), probe these areas:
- User data: "Do you collect or process personal data? Names, emails, IP addresses, device IDs?"
- Geography: "Where are your users? EU (GDPR), California (CCPA), worldwide?"
- Third-party services: "What analytics, payment, or ad SDKs do you use? Each has data implications."
- Open source: "What licenses are in your dependency tree? Any copyleft (GPL, AGPL)?"
- Industry: "Is your project in a regulated domain? (Finance, healthcare, education, children's data)"
Red Flags to Watch For
- PII logged to console, error trackers, or analytics without consent
- GPL/AGPL dependencies in proprietary/commercial software
- No data deletion mechanism (GDPR right to erasure, CCPA right to delete)
- Children's data collected without COPPA compliance
- Missing data processing agreements with third-party vendors
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.
- 12d ago First seen · 129 lines · 26 tokens per session scan A 73032b27302b
afc-legal-expert is an agent published in the GitHub repository jhlee0409/all-for-claudecode (7 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 1,125 once invoked, about $0.0001 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-31.
Other agents, from other repositories
compliance-engineer
SOC2, HIPAA, GDPR, PCI-DSS compliance implementation specialist. Use when implementing audit logging, data encryption, access controls, privacy by design, or preparing for compliance audits. Trigger phrases: SOC2, HIPAA, GDPR, PCI, compliance, audit log, data privacy, encryption, access control, DSAR, consent.
copy-lead
A specialist agent for website copy and audience research. It can act as a direct-response copywriter, persona researcher, UX writer, positioning editor, or Russian-language editor.
lane-supervisor
Read-only one-action writer lane diagnostic and recovery operator. Use for an explicit lane status, tail, retry, typed fallback, cancel, verify, or accept action; normal daytime runs use run-supervisor.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.