Borrowing it
Nothing to install: this file belongs to wbrown/janus-datalog. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wbrown/janus-datalog/main/.claude/skills/datalog/SKILL.mdgit clone --depth 1 https://github.com/wbrown/janus-datalogWrote 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/skills/wbrown/janus-datalog/datalog)<a href="https://agentmods.dev/skills/wbrown/janus-datalog/datalog"><img src="https://agentmods.dev/badge/skills/wbrown/janus-datalog/datalog.svg" alt="Measured on agentmods" 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.00163 | $0.05752 |
| Opus 5 | $0.00081 | $0.02876 |
| Sonnet 5 | $0.00033 | $0.01150 |
| Haiku 4.5 | $0.00016 | $0.00575 |
Grade A, and why
datalog 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 7d 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 — 562 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Datalog Query
Query janus-datalog databases for debugging and data exploration.
The user will provide a database path — a BadgerDB directory, an .edn dump, or a .jdzl (binary) dump — and describe what they want to know. Use the datalog CLI to run queries against the database. A path ending in .edn or .jdzl is loaded into a temporary database automatically (writes are discarded on exit).
Data Model
janus-datalog is a Datomic-style EAV (Entity-Attribute-Value) store. All data is stored as datoms: [entity attribute value tx]. There are no tables — entities are just collections of attribute-value pairs, connected by shared entity IDs.
Attributes follow a namespaced keyword convention: :namespace/name (e.g., :person/name, :order/total). This means attributes cluster by namespace, which is useful when exploring unknown databases.
Storage is CRDT-backed (Conflict-free Replicated Data Types). Every write is preserved with a unique ElementID. Attribute cardinality determines conflict resolution:
| Cardinality | Behavior | Example |
|---|---|---|
| One | Last-Writer-Wins — only the latest value is returned by default | :person/name, :person/age |
| Many | Add-Wins Set — all distinct values are returned | :person/tag, :person/role |
| Vector | RGA — ordered list with deterministic merge | :product/tags, :playlist/songs |
Because all writes are preserved, you can time-travel: db.History() returns all raw datoms (no CRDT resolution), and db.AsOf(elementID) queries CRDT-resolved state as of a specific transaction.
Tool
Binary: ~/go/bin/datalog
Install if missing:
go install github.com/wbrown/janus-datalog/cmd/datalog@latest
Invocation
-db <path> accepts a BadgerDB database directory, an .edn dump file, or a .jdzl (compressed binary) dump file.
# Run a query
~/go/bin/datalog -db <path> -query '<EDN query>'
# With input bindings (repeatable, one per :in parameter after $)
~/go/bin/datalog -db <path> -query '<EDN query with :in>' -in '<EDN value>' [-in '<EDN value>' ...]
# With performance annotations
~/go/bin/datalog -db <path> -verbose -query '<EDN query>'
# Plan without executing: the compiled algebra, every optimizer rewrite
# decision (applied or declined with the reason), and the physical plan
~/go/bin/datalog -db <path> -plan-only -query '<EDN query>'
# Export entire database to readable EDN (useful for small DBs)
~/go/bin/datalog -db <path> -export <output.edn>
# Export to compressed binary JDZL instead (smaller, faster than EDN)
~/go/bin/datalog -db <path> -export-bin <output.jdzl>
# Per-attribute statistics: cardinality, value sizes, duplication, CRDT ops
~/go/bin/datalog -db <path> -stats
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.
- 7d ago First seen · 562 lines · 163 tokens per session scan A 257567275977
datalog is a skill published in the GitHub repository wbrown/janus-datalog (51 stars, last pushed 29d ago), licensed Apache-2.0. It adds 163 tokens to every session and 5,752 once invoked, about $0.0008 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-30.
Other skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
volcengine-rds-postgresql
A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.