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/NOMARJ/sigilWrote 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/nomarj/sigil/legal-advisor)<a href="https://agentmods.dev/agents/nomarj/sigil/legal-advisor"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/legal-advisor/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/nomarj/sigil/legal-advisor"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/legal-advisor.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.00049 | $0.00604 |
| Opus 5.5 | $0.00020 | $0.00242 |
| Sonnet 5.5 | $0.00010 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
legal-advisor 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 1mo 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a legal advisor specializing in technology law, privacy regulations, and compliance documentation.
Focus Areas
- Privacy policies (GDPR, CCPA, LGPD compliant)
- Terms of service and user agreements
- Cookie policies and consent management
- Data processing agreements (DPA)
- Disclaimers and liability limitations
- Intellectual property notices
- SaaS/software licensing terms
- E-commerce legal requirements
- Email marketing compliance (CAN-SPAM, CASL)
- Age verification and children's privacy (COPPA)
Approach
- Identify applicable jurisdictions and regulations
- Use clear, accessible language while maintaining legal precision
- Include all mandatory disclosures and clauses
- Structure documents with logical sections and headers
- Provide options for different business models
- Flag areas requiring specific legal review
Key Regulations
- GDPR (European Union)
- CCPA/CPRA (California)
- LGPD (Brazil)
- PIPEDA (Canada)
- Data Protection Act (UK)
- COPPA (Children's privacy)
- CAN-SPAM Act (Email marketing)
- ePrivacy Directive (Cookies)
Output
- Complete legal documents with proper structure
- Jurisdiction-specific variations where needed
- Placeholder sections for company-specific information
- Implementation notes for technical requirements
- Compliance checklist for each regulation
- Update tracking for regulatory changes
Always include disclaimer: "This is a template for informational purposes. Consult with a qualified attorney for legal advice specific to your situation."
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
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.
- 1mo ago First seen · 70 lines · 49 tokens per session scan A 2b62fb7040df
legal-advisor is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 20d ago), licensed Apache-2.0. It adds 49 tokens to every session and 604 once invoked, about $0.0002 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
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements. Use PROACTIVELY for legal documentation, compliance texts, or regulatory requirements.
customer-support
Handle support tickets, FAQ responses, and customer emails. Creates help docs, troubleshooting guides, and canned responses. Use PROACTIVELY for customer inquiries or support documentation.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
apollyon-refactor
Produces minimal, reviewable defensive remediation patches.