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/parcadei/continuousclaudev4.7/claude-mdgit clone --depth 1 https://github.com/parcadei/ContinuousClaudeV4.7Wrote 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/parcadei/continuousclaudev4.7/claude-md)<a href="https://agentmods.dev/instructions/parcadei/continuousclaudev4.7/claude-md"><img src="https://agentmods.dev/badge/instructions/parcadei/continuousclaudev4.7/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.00776 | $0.00776 |
| Opus 5 | $0.00388 | $0.00388 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
ContinuousClaudeV4.7 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 6d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuous Claude v4.7
Autonomous SDLC pipeline for Claude Code. 9 skills, 2 agents, 5 hooks.
Skills
| Skill | Trigger | Role |
|---|---|---|
/autonomous |
Bounded implementation tasks | ASSESS → PLAN → PREMORTEM → PREPARE → EXECUTE → VALIDATE → EVOLVE |
/autonomous-research |
Open-ended research | Looping research pipeline via Ouros — EVOLVE loops back to PLAN |
/research |
Quick exploration | Single-pass Ouros REPL exploration |
/premortem |
Before implementation | Failure analysis gate — first-principles risk check |
/bootup |
Session start | Assess readiness, route to research/autonomous/review |
/review |
Code review | Structural + semantic review |
/create-handoff |
Session end | Serialize context for next session |
/resume-handoff |
Session start | Resume from handoff document |
/upgrade-harness |
Extend Ouros | Add new external functions to Ouros sandbox |
Agents
| Agent | Role |
|---|---|
worker |
Executes atomic tasks — full autonomy over implementation |
oracle |
External research — docs, APIs, best practices |
Hooks (all .mjs — cross-platform)
| Hook | Event | What it does |
|---|---|---|
status.mjs |
statusLine | Context %, git info, goal from handoffs |
tldr-read.mjs |
PreToolUse:Read | Injects structural nav map for large code files, truncates |
post-edit-diagnostics.mjs |
PostToolUse:Edit|Write|MultiEdit|Update | Type errors + lint after edits |
pre-compact.mjs |
PreCompact | Auto-handoff before context compaction |
auto-handoff-stop.mjs |
Stop | Blocks at 85% context to force handoff |
External Tools (optional, on PATH)
| Tool | What it does |
|---|---|
| bloks | Library knowledge cards — API docs, taste, corrections |
| tldr | Token-efficient code analysis (AST, call graphs, diagnostics) |
| ouros | Sandboxed Python REPL with fork/save/resume |
| fastedit | Fast code editing via merge model (pip install fastedits) |
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.
- 6d ago First seen · 63 lines · 776 tokens per session scan A dafd2ac56114
ContinuousClaudeV4.7 CLAUDE.md is an instructions file published in the GitHub repository parcadei/ContinuousClaudeV4.7 (48 stars, last pushed 4mo ago), licensed MIT. It adds 776 tokens to every session, about $0.0039 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
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.
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).