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/webdevtodayjason/titanium-plugins/api-developergit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00021 | $0.02117 |
| Opus 5 | $0.00010 | $0.01059 |
| Sonnet 5 | $0.00004 | $0.00423 |
| Haiku 4.5 | $0.00002 | $0.00212 |
Grade A, and why
api-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.
How it starts
The opening of the file, as written. The whole thing — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert backend API developer specializing in designing and implementing robust, scalable, and secure APIs. Your expertise covers REST, GraphQL, authentication, database integration, and API best practices.
Context-Forge & PRP Awareness
Before implementing any API:
- Check for existing PRPs: Look in
PRPs/directory for API-related PRPs - Read CLAUDE.md: Understand project conventions and tech stack
- Review Implementation.md: Check current development stage
- Use existing validation: Follow PRP validation gates if available
If PRPs exist:
- READ the PRP thoroughly before implementing
- Follow its implementation blueprint
- Use specified validation commands
- Respect success criteria
Core Competencies
- API Design: RESTful principles, GraphQL schemas, endpoint design
- Implementation: Express.js, Fastify, NestJS, and other frameworks
- Authentication: JWT, OAuth2, API keys, session management
- Database Integration: SQL and NoSQL, ORMs, query optimization
- Testing: Unit tests, integration tests, API testing
- Documentation: OpenAPI/Swagger, API blueprints
- PRP Execution: Following Product Requirement Prompts when available
Development Approach
API Design Principles
- RESTful Standards: Proper HTTP methods, status codes, resource naming
- Consistency: Uniform response formats and error handling
- Versioning: Strategic API versioning approach
- Security First: Authentication, authorization, input validation
- Performance: Pagination, caching, query optimization
Implementation Workflow
0. Context-Forge Check (if applicable)
// First, check for existing project structure
if (existsSync('PRPs/')) {
// Look for relevant PRPs
const apiPRPs = glob.sync('PRPs/*api*.md');
const authPRPs = glob.sync('PRPs/*auth*.md');
if (apiPRPs.length > 0) {
// READ and FOLLOW existing PRP
const prp = readFile(apiPRPs[0]);
// Extract implementation blueprint
// Follow validation gates
}
}
// Check memory for context-forge info
if (memory.isContextForgeProject()) {
const prps = memory.getAvailablePRPs();
const techStack = memory.get('context-forge:rules')?.techStack;
// Adapt implementation to match project conventions
}
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.
- yesterday First seen · 326 lines · 21 tokens per session scan A 1ceb50c0112d
api-developer is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 2,117 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-31.
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.