developer

A developer agent for adding an Idea data structure and a score_idea function to a Python backlog module. The score combines impact, strategic fit, and effort using the specified formula, and the work includes tests.

In plain words
What is it for?
Use it to build the idea-scoring logic in src/backlog.py and check it with tests/test_backlog.py.
Why use it?
It helps implement and verify a consistent way to score backlog ideas instead of calculating each score manually.

Agent

Install

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.

agentmods
npx agentmods add agents/bonigarcia/context-engineering/developer
Clone the repo
git clone --depth 1 https://github.com/bonigarcia/context-engineering
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 52 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00052
Opus 5 $0.00000 $0.00026
Sonnet 5 $0.00000 $0.00010
Haiku 4.5 $0.00000 $0.00005

Measured yesterday against content hash 2800bfc47418, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

ch11/bmad-specialized-agents/_bmad/agents/developer.md · 4 lines

What it actually says

Developer task

Implement Idea and score_idea in src/backlog.py, and verify them with tests/test_backlog.py. Use the formula impact * 5 + strategic_fit * 3 - effort * 2.

Changes

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.

  1. yesterday First seen · 4 lines · 0 tokens per session scan A 2800bfc47418

Subscribe to this mod's changes

developer is an agent published in the GitHub repository bonigarcia/context-engineering (132 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 52 tokens. 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.

Related

Other agents, from other repositories

scrum-leader

Use this agent for sprint planning, backlog grooming, velocity tracking, and agile coaching. Deploy when: (1) Sprint boundaries reached (day 1, 7, 14 of 2-week cycle), (2) Backlog grooming needed or estimation sessions required, (3) Daily standup aggregation and impediment tracking, (4) Velocity drift detected (>15%…

Zeekeey-jpeg/LeRoy-HQ · 145 tokens

triage-labels

Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").

alvinunreal/oh-my-opencode-slim · 0 tokens

conductor

You are the COO of your simulated office. You own EVERY SINGLE INQUIRY — the first prompt and every follow-up prompt in every session. No request bypasses you. You receive all tasks, assess scope, and distribute work to the appropriate team. Trivial queries → delegate to @quick. Skill triggers → route to the…

Zeekeey-jpeg/LeRoy-HQ · 149 tokens

scout

Use this agent when starting any substantial task (3+ steps, multi-file work, or complex workflows). It runs silently in the background via the Task tool with runinbackground: true, monitoring for repeatable patterns, skill gaps, and agent opportunities without interrupting active work. Surface its findings at natural…

Zeekeey-jpeg/LeRoy-HQ · 259 tokens

guardian

Use this agent when: (1) Before ANY git commit or PR creation to audit staged changes, (2) When project cleanup or scope validation is needed, (3) When code quality audit or file organization review is required, (4) Before major release preparation. This agent is MANDATORY in the commit workflow and acts as the final…

Zeekeey-jpeg/LeRoy-HQ · 170 tokens

legal

Use this agent when you need to draft, review, or negotiate contracts for your engagements. This agent handles contract drafting from templates, insurance coverage alignment, clause library cross-referencing, and pre-signing risk assessments. Triggering conditions: User says "draft contract", "new agreement", "create…

Zeekeey-jpeg/LeRoy-HQ · 469 tokens