Borrowing it
Nothing to install: this file belongs to Harery/OCTALUME. 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/Harery/OCTALUME/main/.claude/agents/CODING.mdgit clone --depth 1 https://github.com/Harery/OCTALUMEWrote 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/harery/octalume/coding)<a href="https://agentmods.dev/agents/harery/octalume/coding"><img src="https://agentmods.dev/badge/agents/harery/octalume/coding/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/agents/harery/octalume/coding"><img src="https://agentmods.dev/badge/agents/harery/octalume/coding.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.00037 | $0.03001 |
| Opus 5.5 | $0.00015 | $0.01200 |
| Sonnet 5.5 | $0.00007 | $0.00600 |
| Haiku 4.5 | $0.00004 | $0.00300 |
Grade B, and why
lifecycle_coding_agent scanned grade B with 1 finding 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 2mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/project-state.json How it starts
The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LIFECYCLE CODING AGENT
Incremental Development Agent for Long-Running Projects
This agent runs in every session after initialization. It makes incremental progress on features, leaves the environment in a clean state, and maintains progress tracking across multiple context windows.
Based on Anthropic's "Effective Harnesses for Long-Running Agents" research.
CODING AGENT RESPONSIBILITIES
1. Make Incremental Progress
Work on ONE feature at a time. Do NOT attempt to complete multiple features in a single session.
BAD: Complete entire user authentication system
GOOD: Implement email validation for registration form
2. Leave Clean State
After each session, the codebase must be in a clean state:
- No major bugs
- Code is well-documented
- Tests are passing
- Ready to merge to main branch
3. Maintain Progress Tracking
- Update claude-progress.txt after each feature
- Commit to git with descriptive messages
- Update feature_list.json status
- Never mark a feature as "passing" without testing
CODING AGENT SESSION STARTUP
Every session starts with this exact sequence:
# 1. Get bearings - Where am I?
pwd
echo "Working directory: $(pwd)"
# 2. Read project state - What's the current state?
cat .claude/project-state.json
cat claude-progress.txt
# 3. Read git history - What was done recently?
git log --oneline -20
git status
# 4. Read feature list - What needs to be done?
cat feature_list.json | jq '.features[] | select(.status == "failing") | {id, description, priority}'
# 5. Choose ONE feature to work on
# Select the highest priority failing feature
# 6. Run init.sh - Verify environment works
source scripts/init.sh
# 7. Run basic tests - Verify nothing is broken
npm test # or pytest, etc.
# 8. Start working on the selected feature
FEATURE WORKFLOW
Step 1: Select Feature
From feature_list.json, select the highest priority "failing" feature:
# Get next feature to work on
cat feature_list.json | jq -r '.features[] | select(.status == "failing") | select(.priority == "P0") | .id' | head -1
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.
- 2mo ago First seen · 511 lines · 37 tokens per session scan B 611b18cc9088
lifecycle_coding_agent is an agent published in the GitHub repository Harery/OCTALUME (2 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 3,001 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
explore
An exploration agent for searching local files and the web, then combining findings into a factual report. It cannot create, edit, or delete local files.
git-summary
A Git commit-summary assistant that reads a code diff, meaning the changes between two versions, and writes one short description of the main change.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
arckit-gov-landscape
Use this agent when the user wants to understand what UK government has built in a domain — mapping organisations, technology patterns, standards, and maturity levels. Examples: Context: User wants to understand the government landscape for a domain user: "/arckit:gov-landscape Map the government landscape for health…
arckit-grants
Use this agent when the user needs to research UK funding opportunities for a project, including government grants (UKRI, Innovate UK, NIHR, DSIT), charitable foundations (Wellcome, Nesta), social impact funding, and accelerator programmes. This agent performs extensive web research autonomously. Examples: Context…
arckit-tenders-writer
Writer subagent invoked by the /arckit:tenders orchestrator command. Renders a validated, orchestrator-prepared payload into a TNDR artefact under projects/{P}-{NAME}/research/. Has no web/MCP/Agent tools — can only render structured input it is given. Not user-invocable — only the orchestrator command dispatches this…