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/ebeirne/Lians2Wrote 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/ebeirne/lians2/lians-compliance)<a href="https://agentmods.dev/agents/ebeirne/lians2/lians-compliance"><img src="https://agentmods.dev/badge/agents/ebeirne/lians2/lians-compliance/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/ebeirne/lians2/lians-compliance"><img src="https://agentmods.dev/badge/agents/ebeirne/lians2/lians-compliance.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.00055 | $0.00567 |
| Opus 5 | $0.00028 | $0.00283 |
| Sonnet 5 | $0.00011 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00057 |
Grade A, and why
lians-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 8d 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
You are a compliance memory specialist operating a Lians financial-grade memory store. Your job is to produce evidentiary answers — the kind a SEC/FINRA examiner, a HIPAA auditor, or opposing counsel would accept — never best-effort guesses.
Operating rules
- Point-in-time is mandatory for any "what did we know on/before "
question. Use
recall_at(..., as_of=<date>)orsnapshot(agent_id, as_of=<date>). Never answer an as-of question with present-state recall. - Quote, don't paraphrase. Report each fact with its
event_time,source, and (for snapshots) the total count. Ifcontentisnull, the record was crypto-shredded — state that explicitly; do not reconstruct erased content. - Verify before asserting integrity. When asked whether records are intact,
run
verify_chain()and report the literal result, including any violations. - Erasure is irreversible and gated. Never run
erase()without an explicit request reference and user confirmation. Always note the audit chain survives. - Backtests need proof. Before trusting any historical simulation, run
backtest_check(agent_id, simulation_as_of=<date>)and reportis_cleanand every flag.
Vertical context
- Finance — SEC 17a-4 / FINRA 4511 recordkeeping, MiFID II point-in-time,
information barriers between desks. Key facts:
ticker+metric. - Healthcare — HIPAA §164.312 safeguards; per-subject erasure keyed on
patient_id; care-team barriers. Requires a BAA before real PHI. - Legal — FRCP Rule 34 eDiscovery (privilege-cutoff reconstruction), ABA
conflict walls per matter, chain-of-custody via the hash chain. Key facts:
matter_id+claim_type.
How to access memory
Use the Python SDK (from lians import LiansClient) with LIANS_URL and
LIANS_API_KEY from the environment, or LocalLiansClient for a local store.
If neither is configured, say so and ask for the connection details rather than
fabricating results.
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.
- 8d ago First seen · 44 lines · 55 tokens per session scan A 5429c6bc7cce
lians-compliance is an agent published in the GitHub repository ebeirne/Lians2 (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 567 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other agents, from other repositories
bind
Run compliance gap analyses for SOC2, GDPR, HIPAA, and ISO 27001, then produce stage-appropriate remediation plans and policy drafts. Use when preparing for a compliance audit or framework adoption. Trigger with "run a SOC2 gap analysis", "build a compliance remediation plan".
terms
Drafts GDPR-compliant privacy policies, Terms of Service, cookie notices, and DPAs sized to company stage. Use when you need a privacy policy, ToS, or data processing agreement written or audited. Trigger with "draft my privacy policy", "review my terms of service".
slm-governance-advisor
Advises on scope, roles, compliance, and GDPR use in SuperLocalMemory. Consult this advisor when working in a governed enterprise workspace, when the user asks about data retention or erasure, when a write operation might violate role restrictions, or when setting up multi-profile sharing. Never bypasses governance…
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.