Borrowing it
Nothing to install: this file belongs to prajapatimehul/comp-agent. 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/prajapatimehul/comp-agent/main/CLAUDE.mdgit clone --depth 1 https://github.com/prajapatimehul/comp-agentWrote 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/prajapatimehul/comp-agent/claude-md)<a href="https://agentmods.dev/instructions/prajapatimehul/comp-agent/claude-md"><img src="https://agentmods.dev/badge/instructions/prajapatimehul/comp-agent/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.01839 | $0.01839 |
| Opus 5 | $0.00920 | $0.00920 |
| Sonnet 5 | $0.00368 | $0.00368 |
| Haiku 4.5 | $0.00184 | $0.00184 |
Grade A, and why
comp-agent 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 8d 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 — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CompliancePilot v2
Zero-code AWS compliance engine powered by Claude Code. SOC 2 + HIPAA scanning, remediation, and audit reporting — all driven by configuration files.
Architecture
No application code. Claude Code IS the engine. Configuration files provide:
- Agents (
agents/) — scanner, remediator, auditor - Skills (
skills/) —/scan,/remediate,/posture,/audit-report - Rules (
rules/) — SOC 2 and HIPAA control-to-Prowler-check mappings - Hooks (
hooks/) — AWS guardrail blocking destructive operations - MCP (
.mcp.json) — AWS API access via awslabs MCP server
Directory Structure
.compliance/ # Runtime data (gitignored, created in user's project)
scans/ # Raw Prowler OCSF JSON output
findings/ # One JSON file per failed check: FINDING-{service}-{hash}.json
evidence/ # Before/after state per remediation
reports/ # Generated audit reports
Finding Lifecycle
open → in_progress → remediated → verified
↘ skipped
- open: Prowler detected a failure, finding created
- in_progress: Remediator is working on it
- remediated: Fix applied, awaiting verification
- verified: Re-scan confirms the fix worked
- skipped: User chose to accept the risk
Finding JSON Schema
Each finding is stored as .compliance/findings/FINDING-{service}-{hash}.json:
{
"id": "FINDING-s3-a1b2c3d4",
"scanId": "scan-20260302-143022",
"status": "open",
"source": {
"checkId": "s3_bucket_default_encryption",
"checkTitle": "S3 bucket without default encryption",
"service": "s3",
"severity": "high"
},
"resource": {
"arn": "arn:aws:s3:::my-bucket",
"region": "us-east-1",
"account": "123456789012"
},
"compliance": [
{ "framework": "soc2", "controls": ["CC6.7"] },
{ "framework": "hipaa", "controls": ["164.312(a)(1)"] }
],
"description": "Human-readable description of the issue.",
"remediation": {
"recommendation": "What to do",
"awsCli": "aws ... exact command"
},
"fix": {
"status": "pending",
"proposedAt": null,
"appliedAt": null,
"verifiedAt": null
}
}
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.
- 8d ago First seen · 179 lines · 1,839 tokens per session scan A 0c368320b497
comp-agent CLAUDE.md is an instructions file published in the GitHub repository prajapatimehul/comp-agent (5 stars, last pushed 6mo ago), licensed MIT. It adds 1,839 tokens to every session, about $0.0092 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
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).
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.
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).
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.