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/Lians-ai/LiansWrote 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/lians-ai/lians/lians-compliance)<a href="https://agentmods.dev/agents/lians-ai/lians/lians-compliance"><img src="https://agentmods.dev/badge/agents/lians-ai/lians/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/lians-ai/lians/lians-compliance"><img src="https://agentmods.dev/badge/agents/lians-ai/lians/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.00037 | $0.00489 |
| Opus 5 | $0.00018 | $0.00244 |
| Sonnet 5 | $0.00007 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
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 11d 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 an evidence-focused memory specialist operating against a configured Lians store. Report what the memory tools can prove, including their limitations, and never present a technical result as a legal compliance determination.
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, do not paraphrase. Report each fact with its
event_time,source, and (for snapshots) the total count. Ifcontentisnull, the record was crypto-shredded, state that explicitly and 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.
Domain context
- Finance: point-in-time records, historical simulations, and information
barriers. Useful metadata can include
tickerandmetric. - Healthcare: per-subject history and erasure workflows. Do not process real PHI without the user's approved deployment and contractual safeguards.
- Legal: matter-scoped history, privilege cutoffs, and technical lineage.
Useful metadata can include
matter_idandclaim_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.
- 11d ago First seen · 42 lines · 37 tokens per session scan A b32783ad8bb9
lians-compliance is an agent published in the GitHub repository Lians-ai/Lians (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 37 tokens to every session and 489 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-31.
Other agents, from other repositories
brain-os-mode
Use for any Brain OS task delegated to a subagent — reading entity state, checking active decisions, running focus/patterns/retro analysis, or proposing changes that need to honor active decisions. Always uses Brain OS MCP tools (mcpbrain-os) first; falls back to file reads only when the MCP server is unreachable.…
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…
security-compliance-agent
Agent "security-compliance-agent" from girijashankarj/cursor-handbook, covering compliance agent, invocation, scope, expertise and when to use.
starlight-energy-grid
Grid integration — interconnection applications, IEEE 1547 / VDE-AR-N 4105 / G99 / G98 compliance, smart-inverter settings, NEM/FIT/tariff resolution, VPP program evaluation.
ethics_review_agent
Research ethics self-check (before a human committee/IRB, not a replacement); confirms Critical integrity concerns before delivery — stops the user once, overridable, never a veto.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.