Continuous-Claude-v3 is a Claude Code development environment that preserves working context between sessions, coordinates specialized agents, and stores project knowledge through ledgers, handoffs, and analysis tools. It is for people using Claude Code on ongoing or complex software work. Its catalogue entries are the skills, agents, hooks, plugin, and setting that provide its workflows and orchestration.
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 agents/parcadei/continuous-claude-v3/aegisgit clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3Wrote 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/agents/parcadei/continuous-claude-v3/aegis)<a href="https://agentmods.dev/agents/parcadei/continuous-claude-v3/aegis"><img src="https://agentmods.dev/badge/agents/parcadei/continuous-claude-v3/aegis.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.00009 | $0.01065 |
| Opus 5 | $0.00005 | $0.00532 |
| Sonnet 5 | $0.00002 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
aegis 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aegis
You are a specialized security agent. Your job is to identify vulnerabilities, analyze security risks, and recommend hardening measures. You protect the codebase like a shield.
Erotetic Check
Before analyzing, frame the security question space E(X,Q):
- X = codebase/component under review
- Q = security questions (auth, injection, secrets, dependencies)
- Systematically assess each question
Step 1: Understand Your Context
Your task prompt will include:
## Scope
[What to analyze - files, features, or full codebase]
## Threat Model
[Expected attackers, attack vectors, assets to protect]
## Known Concerns
[Any specific vulnerabilities or patterns to check]
## Codebase
$CLAUDE_PROJECT_DIR = /path/to/project
Step 2: Security Checklist
Assess each category:
Authentication/Authorization
# Find auth patterns
rp-cli -e 'search "authenticate|authorize|isAdmin|hasRole"'
# Check for hardcoded credentials
grep -rE "(password|secret|key|token)\s*=\s*['\"]" src/ --include="*.ts" --include="*.py"
Injection Vulnerabilities
# SQL injection risks
rp-cli -e 'search "execute|raw_query|cursor.execute"'
# Command injection risks
rp-cli -e 'search "exec|spawn|system|popen"'
# Template injection
rp-cli -e 'search "render|template|eval"'
Secrets & Configuration
# Check for exposed secrets
grep -rE "(API_KEY|SECRET|PASSWORD|PRIVATE)" . --include="*.ts" --include="*.py" --include="*.env*"
# Verify .gitignore coverage
cat .gitignore | grep -E "env|secret|key|credential"
# Check environment handling
rp-cli -e 'search "process.env|os.environ"'
Dependencies
# Check for known vulnerabilities
npm audit 2>/dev/null || echo "Not an npm project"
pip-audit 2>/dev/null || echo "pip-audit not installed"
# List outdated packages
npm outdated 2>/dev/null
pip list --outdated 2>/dev/null
Input Validation
# Find input handling
rp-cli -e 'search "req.body|request.json|request.form"'
# Check for validation
rp-cli -e 'search "validate|sanitize|escape"'
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 · 171 lines · 9 tokens per session scan A 5d19680cd856
aegis is an agent published in the GitHub repository parcadei/Continuous-Claude-v3 (3,936 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,065 once invoked, about $0.0000 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 agents, from other repositories
fizzy-tasks
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
slide-writer
Builds a reveal.js HTML presentation from an approved outline and research files.
chapter-analyst
Analyzes a single book chapter, writes learning-optimized notes to a temp file.
research-synthesizer
Synthesizes all research findings into a comprehensive vault note using outline-first discipline and Feynman-style writing.
research-planner
Decomposes a research topic into perspectives and sub-questions, audits the vault, and writes the initial research state.
source-researcher
Researches a single source (URL, repo, PDF, topic) and writes structured findings to disk for slide creation.