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/commands/lians-ai/lians/lians-audit)<a href="https://agentmods.dev/commands/lians-ai/lians/lians-audit"><img src="https://agentmods.dev/badge/commands/lians-ai/lians/lians-audit/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/commands/lians-ai/lians/lians-audit"><img src="https://agentmods.dev/badge/commands/lians-ai/lians/lians-audit.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.00020 | $0.00460 |
| Opus 5 | $0.00010 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
lians-audit 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 10d 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
/lians-audit
Run Lians operations that produce technical evidence about memory state. Parse the operation from $ARGUMENTS and execute the matching call. Always print exactly what was returned, including limitations. Do not claim that a technical result establishes legal or regulatory compliance.
Operations
snapshot <agent_id> <YYYY-MM-DD>
Exhaustive knowledge-state reconstruction - every fact valid at that instant, not a ranked top-k. The one-call demo for "show me everything the agent knew on 2025-03-14."
snap = mem.snapshot(agent_id="<agent>", as_of=datetime(...))
print(snap["total"], "facts valid at", snap["as_of"])
verify
Verify the tamper-evident SHA-256 hash chain. Report any broken link exactly as the tool returns it.
print(mem.verify_chain()) # {"status": "ok", "rows_checked": N, "violations": []}
backtest <agent_id> <YYYY-MM-DD>
Lookahead-bias detection - flags any fact the agent held that it could not have known at the simulation date. A clean report shows that this check found no lookahead flags; it does not validate the entire simulation.
r = mem.backtest_check(agent_id="<agent>", simulation_as_of=datetime(...))
print("clean" if r["is_clean"] else f"{len(r['flags'])} contamination flags")
erase <subject_id> <request_ref>
Destroys the subject's per-subject key so their encrypted content becomes
unreadable while the audit hash chain survives. This is irreversible. Confirm
with the user before running, and record the request_ref.
print(mem.erase(subject_id="<subject>", request_ref="<ref>"))
If the operation isn't recognized, list these four and ask which one.
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.
- 10d ago First seen · 49 lines · 20 tokens per session scan A dc394c695d0b
lians-audit is a command published in the GitHub repository Lians-ai/Lians (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 460 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 commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
decide
Capture a strategic decision so it never gets lost or reopened accidentally.
scorecard
Run a repeatable weekly health check. Score Brain OS out of 100. Compare week-over-week.
preflight
Audit a build against App Review rejection triggers by app type before submitting.
rejection-recovery
Diagnose an App Review rejection, draft a Resolution Center response, and plan the fix.
docs-health-checks
Open ArchiPy app health-check guidance for HTTP and gRPC liveness, readiness, startup probes, and shutdown.