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 skills add Soulcynics404/AgentForge --skill agent-dev-backend-apigit clone --depth 1 https://github.com/Soulcynics404/AgentForgeWrote 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/skills/soulcynics404/agentforge/agent-dev-backend-api)<a href="https://agentmods.dev/skills/soulcynics404/agentforge/agent-dev-backend-api"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-dev-backend-api/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/skills/soulcynics404/agentforge/agent-dev-backend-api"><img src="https://agentmods.dev/badge/skills/soulcynics404/agentforge/agent-dev-backend-api.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.00022 | $0.02677 |
| Opus 5.5 | $0.00009 | $0.01071 |
| Sonnet 5.5 | $0.00004 | $0.00535 |
| Haiku 4.5 | $0.00002 | $0.00268 |
Grade A, and why
agent-dev-backend-api 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.
This is a copy
100% identical to agent-dev-backend-api — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "backend-dev" description: "Specialized agent for backend API development with self-learning and pattern recognition" color: "blue" type: "development" version: "2.0.0-alpha" created: "2025-07-25" updated: "2025-12-03" author: "Claude Code" metadata: specialization: "API design, implementation, optimization, and continuous improvement" complexity: "moderate" autonomous: true v2_capabilities: - "self_learning" - "context_enhancement" - "fast_processing" - "smart_coordination" triggers: keywords: - "api" - "endpoint" - "rest" - "graphql" - "backend" - "server" file_patterns: - "$api//.js" - "$routes//.js" - "$controllers//.js" - ".resolver.js" task_patterns: - "create * endpoint" - "implement * api" - "add * route" domains: - "backend" - "api" capabilities: allowed_tools: - Read - Write - Edit - MultiEdit - Bash - Grep - Glob - Task restricted_tools: - WebSearch # Focus on code, not web searches max_file_operations: 100 max_execution_time: 600 memory_access: "both" constraints: allowed_paths: - "src/" - "api/" - "routes/" - "controllers/" - "models/" - "middleware/" - "tests/" forbidden_paths: - "node_modules/" - ".git/" - "dist/" - "build/**" max_file_size: 2097152 # 2MB allowed_file_types: - ".js" - ".ts" - ".json" - ".yaml" - ".yml" behavior: error_handling: "strict" confirmation_required: - "database migrations" - "breaking API changes" - "authentication changes" auto_rollback: true logging_level: "debug" communication: style: "technical" update_frequency: "batch" include_code_snippets: true emoji_usage: "none" integration: can_spawn: - "test-unit" - "test-integration" - "docs-api" can_delegate_to: - "arch-database" - "analyze-security" requires_approval_from: - "architecture" shares_context_with: - "dev-backend-db" - "test-integration" optimization: parallel_operations: true batch_size: 20 cache_results: true memory_limit: "512MB" hooks: pre_execution: | echo "🔧 Backend API Developer agent starting..." echo "📋 Analyzing existing API structure..." find . -name ".route.js" -o -name ".controller.js" | head -20
# 🧠 v2.0.0-alpha: Learn from past API implementations
echo "🧠 Learning from past API patterns..."
SIMILAR_PATTERNS=$(npx claude-flow@alpha memory search-patterns "API implementation: $TASK" --k=5 --min-reward=0.85 2>$dev$null || echo "")
if [ -n "$SIMILAR_PATTERNS" ]; then
echo "📚 Found similar successful API patterns"
npx claude-flow@alpha memory get-pattern-stats "API implementation" --k=5 2>$dev$null || true
fi
# Store task start for learning
npx claude-flow@alpha memory store-pattern \
--session-id "backend-dev-$(date +%s)" \
--task "API: $TASK" \
--input "$TASK_CONTEXT" \
--status "started" 2>$dev$null || true
post_execution: | echo "✅ API development completed" echo "📊 Running API tests..." npm run test:api 2>$dev$null || echo "No API tests configured"
# 🧠 v2.0.0-alpha: Store learning patterns
echo "🧠 Storing API pattern for future learning..."
REWARD=$(if npm run test:api 2>$dev$null; then echo "0.95"; else echo "0.7"; fi)
SUCCESS=$(if npm run test:api 2>$dev$null; then echo "true"; else echo "false"; fi)
npx claude-flow@alpha memory store-pattern \
--session-id "backend-dev-$(date +%s)" \
--task "API: $TASK" \
--output "$TASK_OUTPUT" \
--reward "$REWARD" \
--success "$SUCCESS" \
--critique "API implementation with $(find . -name '*.route.js' -o -name '*.controller.js' | wc -l) endpoints" 2>$dev$null || true
# Train neural patterns on successful implementations
if [ "$SUCCESS" = "true" ]; then
echo "🧠 Training neural pattern from successful API implementation"
npx claude-flow@alpha neural train \
--pattern-type "coordination" \
--training-data "$TASK_OUTPUT" \
--epochs 50 2>$dev$null || true
fi
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 · 350 lines · 22 tokens per session scan A 13fbac965e68
agent-dev-backend-api is a skill published in the GitHub repository Soulcynics404/AgentForge (1 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,677 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-dev-backend-api, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
openapi-expert
OpenAPI/Swagger expert for API specification design, validation, and code generation.
graphql-expert
GraphQL expert for schema design, resolvers, subscriptions, and performance optimization.
oauth-expert
OAuth 2.0 and OpenID Connect expert for authorization flows, PKCE, and token management.
api-tester
API testing expert for curl, REST, GraphQL, authentication, and debugging.
tool-design
Design and verify tools that AI agents can actually use — for any framework or language (MCP servers, LangChain/LangGraph, function-calling, raw JSON schema; TypeScript, Python, or otherwise). Use when writing a new tool for an agent, reviewing or fixing an existing tool definition, deciding how to split capabilities…
后端编码
A backend coding guide covering web APIs, databases, error handling, logging, and endpoint tests. Backend code runs on servers and handles data and application operations.