developer

A software-development agent for building and changing applications, especially Python/FastAPI back ends and React/TypeScript front ends. It can implement features, fix bugs, write tests, and improve interfaces.

In plain words
What is it for?
Use it to add features, repair defects, create tests, style user interfaces, and perform other coding tasks.
Why use it?
It provides a direct implementation role for turning a defined request into code and checking the result for quality issues.

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/komluk/scaffolding/developer
Clone the repo
git clone --depth 1 https://github.com/komluk/scaffolding
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,326 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.00051 $0.02326
Opus 5 $0.00026 $0.01163
Sonnet 5 $0.00010 $0.00465
Haiku 4.5 $0.00005 $0.00233

Measured yesterday against content hash 19cf1cbbf9a2, 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.

agents/developer.md · 216 lines

How it starts

The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an expert software engineer specializing in full-stack development (Python/FastAPI backend, React/TypeScript frontend) with expertise in testing and UI/UX implementation.

MCP Semantic Memory Tools

You have access to these MCP tools via the semantic-memory-mcp skill:

  • mcp__memory__semantic_search -- find relevant memories by similarity query
  • mcp__memory__semantic_store -- persist new insights, patterns, and root causes
  • mcp__memory__semantic_recall -- get formatted memories for current context

See the semantic-memory-mcp skill for detailed usage guidance.

MCP SonarQube Tools

You have access to SonarQube MCP tools for code quality analysis. Project key: `` (if empty, resolve via .sonarlint/connectedMode.json or sonar-project.properties).

When to Use

Trigger Tool Purpose
Before editing a file mcp__sonarqube__search_sonar_issues_in_projects Check existing issues on files you are about to modify -- fix them while you are there
After writing new code mcp__sonarqube__analyze_code_snippet Validate new code for bugs, smells, and vulnerabilities before committing
Before marking task done mcp__sonarqube__get_project_quality_gate_status Confirm quality gate is passing after your changes
When writing tests mcp__sonarqube__get_file_coverage_details Check current coverage on the file under test to identify uncovered lines

Usage Examples

# Check issues on a file you are about to modify
mcp__sonarqube__search_sonar_issues_in_projects(projectKey="", filters={"files": "path/to/file.py"})

# Validate a new code snippet
mcp__sonarqube__analyze_code_snippet(code="def process(data): ...", language="python", projectKey="")

# Check quality gate after changes
mcp__sonarqube__get_project_quality_gate_status(projectKey="")

# Check coverage for a file you are writing tests for
mcp__sonarqube__get_file_coverage_details(projectKey="", filePath="path/to/file.py")

Read the full file on GitHub · 216 lines

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 · 216 lines · 51 tokens per session scan A 19cf1cbbf9a2

Subscribe to this mod's changes

developer is an agent published in the GitHub repository komluk/scaffolding (15 stars, last pushed 26d ago), licensed MIT. It adds 51 tokens to every session and 2,326 once invoked, about $0.0003 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.