Borrowing it
Nothing to install: this file belongs to shinyobjectz/montology. 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/shinyobjectz/montology/main/CLAUDE.mdgit clone --depth 1 https://github.com/shinyobjectz/montologyWrote 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/shinyobjectz/montology/claude-md)<a href="https://agentmods.dev/instructions/shinyobjectz/montology/claude-md"><img src="https://agentmods.dev/badge/instructions/shinyobjectz/montology/claude-md/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/instructions/shinyobjectz/montology/claude-md"><img src="https://agentmods.dev/badge/instructions/shinyobjectz/montology/claude-md.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.00483 | $0.00483 |
| Opus 5.5 | $0.00193 | $0.00193 |
| Sonnet 5.5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
montology CLAUDE.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 1mo 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
montology — repo instructions
Public repo, shinyobjectz/montology. Also mounted as a submodule of the
private socialite repo — never assume socialite's code or vocabulary is
reachable from here; this repo stands alone.
What this is: the ontology context layer for any monorepo — a
vocabulary as a database, enforced against the code by a tree-sitter scan.
Nothing else. This repo had a marketing-tool past; none of that
vocabulary belongs here, and it is not to be resurrected. The one thing
kept from it is the public-taxonomy registry (monty onto sources),
which is about other people's standards, not that era's product.
The shape
.monty/core— workspace discovery (walk up for.monty, like git)..monty/onto— the database: word / doctrine / overload / gen_runs. Montology's own words are authored ONLY inseed.py(just seed)..monty/scan— the multiast layer: tree-sitter declarations per language, the lint (collision / code-resolution / drift), candidates mining, ast-grep invoked for structural search..monty/gen—sync(deterministic render of the words skill),gen_word(atomic-tier drafts under law),lint(the drift gate + the no-prompt ban)..monty/cli—monty;.plugin/— the Agent Plugins face;npm/— the launcher.
Ground rules
- Dogfood: this repo is itself a montology workspace.
monty onto check <name>before naming anything;just checkrunsmonty lint, so a collision or a stale words skill fails the build here too. - Prose is rendered, never authored.
.claude/skills/words/SKILL.mdis GENERATED (monty sync); hand edits are lost and lint catches them. - Errors are data with the repair attached. A word means one thing. Vendors are not vocabulary.
- This repo is public: nothing tenant-specific, nothing credentialed, nothing from socialite's private tree crosses into it.
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.
- 1mo ago Changed · +2 lines · +39 tokens per session f8251503ace6
- 1mo ago First seen · 37 lines · 444 tokens per session scan A a552d6c4fd87
montology CLAUDE.md is an instructions file published in the GitHub repository shinyobjectz/montology (52 stars, last pushed 16d ago), licensed Apache-2.0. It adds 483 tokens to every session, about $0.0019 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-08-31.
Other instructions, from other repositories
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.