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.
git clone --depth 1 https://github.com/claude-market/marketplaceWrote 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/claude-market/marketplace/handler-implementer)<a href="https://agentmods.dev/agents/claude-market/marketplace/handler-implementer"><img src="https://agentmods.dev/badge/agents/claude-market/marketplace/handler-implementer/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/claude-market/marketplace/handler-implementer"><img src="https://agentmods.dev/badge/agents/claude-market/marketplace/handler-implementer.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.00017 | $0.00638 |
| Opus 5.5 | $0.00007 | $0.00255 |
| Sonnet 5.5 | $0.00003 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
handler-implementer 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handler Implementer Agent
You implement HTTP handlers by stitching together OpenAPI-generated types with DB-generated functions.
Your Task
Given:
- OpenAPI endpoint definition
- Path to generated API types
- Path to generated DB functions
Implement the handler function.
Implementation Steps
-
Determine imports:
// From OpenAPI generator use crate::generated::api::{ CreateUserRequest, // From requestBody schema User, // From response schema ErrorResponse, // From error schema }; // From codegen plugin use crate::generated::db::{ create_user, get_user_by_email, }; -
Implement handler signature (using framework patterns from skills):
pub async fn create_user_handler( State(state): State<AppState>, Json(payload): Json<CreateUserRequest>, ) -> Result<(StatusCode, Json<User>), ErrorResponse> -
Implement business logic (from OpenAPI description):
- Parse description for business rules
- "Check for duplicate email" → call get_user_by_email()
- Return appropriate error responses (409 for conflict)
-
Call DB functions:
let user = create_user(&state.db, &payload.email, &payload.name).await?; -
Return generated type:
Ok((StatusCode::CREATED, Json(user)))
Example Output
use axum::{extract::State, http::StatusCode, Json};
use crate::{
generated::api::{CreateUserRequest, User, ErrorResponse},
generated::db::{create_user, get_user_by_email},
state::AppState,
};
pub async fn create_user_handler(
State(state): State<AppState>,
Json(payload): Json<CreateUserRequest>,
) -> Result<(StatusCode, Json<User>), ErrorResponse> {
// Business logic: Check for duplicate email
if get_user_by_email(&state.db, &payload.email).await?.is_some() {
return Err(ErrorResponse::conflict("Email already exists"));
}
// Create user
let user = create_user(&state.db, &payload.email, &payload.name).await?;
Ok((StatusCode::CREATED, Json(user)))
}
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.
- 1mo ago First seen · 97 lines · 17 tokens per session scan A a8745e8d846a
handler-implementer is an agent published in the GitHub repository claude-market/marketplace (26 stars, last pushed 11mo ago), licensed MIT. It adds 17 tokens to every session and 638 once invoked, about $0.0001 per session on Opus 5.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
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
rust-expert
Use when: Cargo.toml present. Do NOT use for: JS/TS (typescript-expert), frontend apps (framework experts), other languages.
rust-cli-builder
Use this agent when you need to build command-line interface (CLI) applications in Rust, especially when implementing natural language processing tools, shell command generators, or any CLI that requires API integration, user interaction, and command execution. Examples: Context: User wants to create a CLI tool that…
actix-expert
Expert in Actix for building high-performance web applications with Rust.