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.
npx skills add orneryd/NornicDB --skill knowledge-policiesgit clone --depth 1 https://github.com/orneryd/NornicDBWrote 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/orneryd/nornicdb/knowledge-policies)<a href="https://agentmods.dev/skills/orneryd/nornicdb/knowledge-policies"><img src="https://agentmods.dev/badge/skills/orneryd/nornicdb/knowledge-policies/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/skills/orneryd/nornicdb/knowledge-policies"><img src="https://agentmods.dev/badge/skills/orneryd/nornicdb/knowledge-policies.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.00087 | $0.05369 |
| Opus 5.5 | $0.00035 | $0.02148 |
| Sonnet 5.5 | $0.00017 | $0.01074 |
| Haiku 4.5 | $0.00009 | $0.00537 |
Grade A, and why
nornicdb-knowledge-policies 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 13d 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 — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NornicDB Knowledge-Layer Policies (Cypher API)
NornicDB scores every node and edge through a Cypher-controlled pipeline. The mental model is Neo4j Cypher: CREATE/ALTER/DROP/SHOW statements plus CALL procedures.
The four object kinds (and exactly what each one does)
There is one targeting mechanism (FOR (...)) used in two places. Object kinds:
| Kind | Carries a target? | What it does | Effect on scores by itself |
|---|---|---|---|
Decay bundle — CREATE DECAY PROFILE <name> OPTIONS { ... } |
No | Names a reusable parameter set: halfLifeSeconds, function, visibilityThreshold, scoreFloor, scope, scoreFrom, scoreFromProperty |
None. A bundle on its own is inert. |
Decay binding — CREATE DECAY PROFILE <name> FOR (...) APPLY { ... } |
Yes (FOR) |
Attaches decay math to a label / multi-label / edge type / wildcard. The APPLY block either references a bundle (DECAY PROFILE 'name') or sets parameters inline, plus per-property overrides. |
Decay is active for entities matching FOR. |
Promotion profile — CREATE PROMOTION PROFILE <name> OPTIONS { ... } |
No | Names a reusable boost: multiplier, scoreFloor, scoreCap, scope. |
None on its own. |
Promotion policy — CREATE PROMOTION POLICY <name> FOR (...) APPLY { ON ACCESS { ... } WHEN ... APPLY PROFILE '...' } |
Yes (FOR) |
Attaches access-counter mutations and conditional boosts to a target. ON ACCESS mutations write to access metadata; WHEN clauses select which promotion profile applies. | Mutates access metadata; promotion math applies when a WHEN matches. |
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.
- 13d ago Changed · -6 tokens per session 8b7f2cab6a34
- 1mo ago Changed · +18 lines 363ac72f1ef9
- 1mo ago First seen · 349 lines · 93 tokens per session scan A 2ab34f183cb0
nornicdb-knowledge-policies is a skill published in the GitHub repository orneryd/NornicDB (916 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 5,369 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
payload
Use when working with Payload projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
graphjin-env
Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.
infrahub-sot
OpsMill Infrahub — infrastructure source of truth with schema-driven nodes, GraphQL queries, and branch-isolated changes. Use when querying Infrahub for device/IPAM inventory, browsing infrastructure schemas, running GraphQL queries, or making infrastructure changes safely via an auto-created session branch and a…
deduplicate
Detect duplicate entities, duplicate groups, and relationship duplicates in VeritasReason using fuzzy matching, schema heuristics, and graph similarity.
change
Track and inspect graph changes, diffs, temporal updates, and the impact of new data on VeritasReason knowledge graphs.