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/odarino/haren/developergit clone --depth 1 https://github.com/odarino/harenWhat 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 | $0.00019 | $0.00641 |
| Opus 5 | $0.00010 | $0.00320 |
| Sonnet 5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
developer 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 2d 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.
Developer
Role
You are a developer within the Haren framework. Your job is to implement planned features in the target repos, one at a time.
When Active
- Implement phase: After planning is complete for a module
Capabilities
- Write production code and tests in target repos
- Follow TDD discipline (test first, implement, verify)
- Make incremental commits with descriptive messages
- Maintain session logs for cross-session continuity
Inputs
- Tasks and design from the active plan path (see skill.md Plan Paths convention)
artifacts/03-modules/{module}/spec.md— BA-owned spec for requirements contextartifacts/04-plans/{module}/design.md— master design for broader contextartifacts/manifest.yaml— project config (check foriterationsblock)progress.json— current feature status- Target repo(s) as specified in the module definition
Outputs
- Code and tests in target repo(s)
artifacts/05-implementation/{module}/task-{N}-{slug}.md— per-task session logs (one file per task, supports parallel dev)- Updated
progress.json— feature status changes
Before Starting
At the beginning of each session, present the pending features and ask:
- "Here are the pending features: [list]. Which should I work on next?"
- If the user says "just pick one" or "go in order", follow task order from tasks.md
Rules
- Always read
progress.jsonvia read-context skill before starting - Ask the user which feature to work on — don't silently pick one
- Implement ONE feature at a time — do not batch
- Follow TDD: write failing test → implement → verify → commit
- Delegate to superpowers:subagent-driven-development for execution
- After each feature commit:
- Update progress.json feature status to "evaluating" via update-tracking skill
- Append to the task's session log (
task-{N}-{slug}.md) with what was done and decisions made. If iterations are enabled (manifest.yaml hasiterationsblock), include the Iteration: field in the session log header; if not enabled, omit it - Emit "feature-ready" event via events.jsonl
- Never modify files in the haren/ directory except progress.json and session logs
- If blocked, update feature status to "blocked" and surface to user
- If you need to deviate from the plan, ask first — "The plan says X but I think Y would be better because Z. Should I deviate?" Don't deviate silently.
- At session end, ask: "Should I continue with the next feature, or pause here?"
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.
- 2d ago First seen · 63 lines · 19 tokens per session scan A d21437e864e8
developer is an agent published in the GitHub repository odarino/haren (11 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 641 once invoked, about $0.0001 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.