Borrowing it
Nothing to install: this file belongs to cryndoc/polisade-orchestrator. 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/cryndoc/polisade-orchestrator/main/CLAUDE.mdgit clone --depth 1 https://github.com/cryndoc/polisade-orchestratorWrote 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/cryndoc/polisade-orchestrator/claude-md)<a href="https://agentmods.dev/instructions/cryndoc/polisade-orchestrator/claude-md"><img src="https://agentmods.dev/badge/instructions/cryndoc/polisade-orchestrator/claude-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.1 | $0.00444 | $0.00444 |
| Opus 5 | $0.00222 | $0.00222 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
polisade-orchestrator 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 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.
What it actually says
CLAUDE.md
You are looking at a release snapshot of the Polisade Orchestrator
plugin (polisade). This repository is published as a read-only mirror:
each release is a single orphan commit with the source tree at that
release plus the four distribution zips attached to the GitHub
Release. Day-to-day development, issue tracking, and PR review happen
in a separate private work repository.
What this repo is for
- End users — install the plugin (
/plugin marketplace add cryndoc/polisade-orchestratorfor Claude Code, or download the Qwen / GigaCode / opencode build zip from a GitHub Release). - Readers — inspect the source of the current release (
skills/,scripts/,tools/). All behaviour lives in Markdown + Python stdlib — nothing hidden.
What this repo is not
- Not the source of truth for ongoing development.
git pullwill not fast-forward — each release force-pushes a new orphan commit. - Not the primary tracker. Issues you file here are mirrored into a
private work repo where triage and development happen; when a fix
ships, the issue is closed with the
polisaderelease that resolves it. Please don't paste internal project paths, proprietary stack traces, secrets, or customer-identifying information into Issues or Discussions.
How to give feedback
- Bug reports & feature requests → Issues (keep them free of internal / sensitive data — see CONTRIBUTING.md)
- Questions, usage help → Discussions → Q&A
- Release announcements → Discussions → Announcements
See CONTRIBUTING.md for the full policy.
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 · 36 lines · 444 tokens per session scan A fad48c1aec8a
polisade-orchestrator CLAUDE.md is an instructions file published in the GitHub repository cryndoc/polisade-orchestrator (7 stars, last pushed 11d ago), licensed Apache-2.0. It adds 444 tokens to every session, about $0.0022 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 instructions, from other repositories
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.
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.
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).
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).
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.
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.