Borrowing it
Nothing to install: this file belongs to priyansh-narang2308/TheBlacklisted-NitroStack. 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/priyansh-narang2308/TheBlacklisted-NitroStack/main/CLAUDE.mdgit clone --depth 1 https://github.com/priyansh-narang2308/TheBlacklisted-NitroStackWrote 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/priyansh-narang2308/theblacklisted-nitrostack/claude-md)<a href="https://agentmods.dev/instructions/priyansh-narang2308/theblacklisted-nitrostack/claude-md"><img src="https://agentmods.dev/badge/instructions/priyansh-narang2308/theblacklisted-nitrostack/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/priyansh-narang2308/theblacklisted-nitrostack/claude-md"><img src="https://agentmods.dev/badge/instructions/priyansh-narang2308/theblacklisted-nitrostack/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.00836 | $0.00836 |
| Opus 5 | $0.00418 | $0.00418 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
TheBlacklisted-NitroStack 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 11d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Protocol-0 (Autonomous SRE Copilot, MCP Server)
What this project is
Protocol-0 is an MCP server built on the Nitrostack platform (SDK + CLI). It exposes an autonomous Site Reliability Engineering (SRE) and Incident Response workflow as MCP Tools, Resources, and Prompts. The MCP client (NitroChat / Claude) is the agent; this server is the capability layer.
THE GOLDEN PATH (the only scope)
start_monitoring → detect_anomaly → trigger_incident_commander → pull_infrastructure_metrics ⚿ → compute_heuristics → assess_business_impact → generate_remediation_plan → execute_action ⚿ → log_audit_event ⚿ = zero-trust-gated: MUST return {error:"ZERO_TRUST_VIOLATION", hint:"..."} without a valid cryptographic payload match. This gate is the project's signature feature.
Non-negotiable rules for Claude Code
- NEVER invent Nitrostack SDK/CLI APIs from memory. The ONLY sources of truth are:
CLI
--help, and.d.tsinnode_modules/@nitrostack/*.- Decorators:
@Tool/@ToolDecorator,@Resource,@Prompt,@Widget,@Module,@McpApp,@HealthCheck,@UseGuards,@UseFilters,@Injectable. - ExecutionContext carries NO tool input (
requestId, toolName, logger, metadata, auth, task). A Guard cannot read azero_trust_tokentool arg → THE ZERO TRUST GATE IS ENFORCED INLINE as the first line of each gated handler, not as a Guard. Guards stay for header/auth checks only.
- Decorators:
- Test-first for the zero trust gate.
tests/zero-trust.test.tsmust exist and pass before any gated tool is written. Runner: vitest (scaffold ships none). - All external data is deterministic mocks in
mocks/*.json. Never call real Datadog/AWS APIs. Never use real PII anywhere. - Canonical tool name is
simulate_disaster(NOT disaster_sim). - Mock outcome mapping (canonical): Incident CPU > 90% = CRITICAL, CPU > 75% = WARNING.
- Every new library/dataset/API goes into THIRD_PARTY.md in the SAME commit.
- Keep it boring: plain TypeScript on the Nitrostack scaffold, in-memory stores. No databases, no ORMs, no extra frameworks.
- Decisioning is rules + a pre-baked scorecard + reason codes. NEVER trained ML. Pure deterministic logic in
src/lib/scorecard.ts. - Redact PII in every audit payload before storage.
- After the
freezetag, only fix bugs that break the golden path. No refactors.
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.
- 11d ago First seen · 59 lines · 836 tokens per session scan A 3b17a2ee2ee5
TheBlacklisted-NitroStack CLAUDE.md is an instructions file published in the GitHub repository priyansh-narang2308/TheBlacklisted-NitroStack (5 stars, last pushed 1mo ago), licensed MIT. It adds 836 tokens to every session, about $0.0042 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).
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.
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).