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 agentmods add instructions/panaversity/ksor/agents-mdgit clone --depth 1 https://github.com/panaversity/ksorWrote 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/instructions/panaversity/ksor/agents-md)<a href="https://agentmods.dev/instructions/panaversity/ksor/agents-md"><img src="https://agentmods.dev/badge/instructions/panaversity/ksor/agents-md.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 | $0.29014 | $0.29014 |
| Opus 5 | $0.14507 | $0.14507 |
| Sonnet 5 | $0.05803 | $0.05803 |
| Haiku 4.5 | $0.02901 | $0.02901 |
Grade A, and why
ksor AGENTS.md 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 today.
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 — 1,811 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
The durable contract for working in this repository: what ksor is, the
vocabulary, the decisions, the invariants, and how it is built and tested.
Loaded every session, so it holds only what stays true — what is true this
week lives in docs/status.md; the product pitch lives in
README.md, its only home.
CLAUDE.md is a symlink to this file. They are the same file: one contract for every agent — human-readable and agent-readable, like everything else here.
Critical rules
- Never weaken provenance, citation, abstention, or governance guarantees to simplify an implementation. They are the product, not features of it.
- Never push directly to
main. Every change lands through a pull request. - Never break the agent-discoverable surfaces: docs bundled in the npm
package (
packages/ksor/docs/), and — once the site ships — itsllms.txtand/.well-known/mcp/server.json. Agents finding ksor is how ksor gets used.
What this is, in one line
A CLI (ksor — the npm package is @panaversity/ksor) that compiles a folder
of governed markdown into two surfaces — a static website for people and an MCP
server for AI agents — with cited answers and honest abstention. It is not an
agent framework; it is the knowledge layer agent frameworks read from.
Which verbs are implemented is not recorded here. This file describes what
ksor is; docs/status.md holds what is built this week. One rule keeps the
CLI itself the current answer: an unimplemented verb says so and exits 2, an
unknown word is refused with exit 1 — so no document has to be kept in step
with the binary.
A Python-era predecessor (vsor, panaversity/zia-vsor-sdk) proved much of the
design. Its work may be taken and converted to TypeScript (decision 6), but it
is a source to mine, not an authority to follow: nothing crosses without asking
what it was for, and converted code re-earns its place with tests here.
What we claim, and to whom
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.
- today Changed · +100 lines · +1,731 tokens per session 9a225d859a31
- 5d ago First seen · 1,711 lines · 27,283 tokens per session scan A 5c66392488b6
ksor AGENTS.md is an instructions file published in the GitHub repository panaversity/ksor (145 stars, last pushed yesterday), licensed Apache-2.0. It adds 29,014 tokens to every session, about $0.1451 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 instructions, from other repositories
AI-Governance-Architecture CLAUDE.md
Claude Code instructions for war851/AI-Governance-Architecture, covering project: governed ai, stack: tbd — project-agnostic baseline, environment: windows 10 · powershell · cursor + claude code, architecture overview and application design.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).