Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSnpx agentmods add agents/dds-solutions/ai-tadpole-os/tadpole-backend-specialistWrote 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/dds-solutions/ai-tadpole-os/tadpole-backend-specialist)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/tadpole-backend-specialist"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/tadpole-backend-specialist/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/dds-solutions/ai-tadpole-os/tadpole-backend-specialist"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/tadpole-backend-specialist.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.00045 | $0.01244 |
| Opus 5 | $0.00023 | $0.00622 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
tadpole-backend-specialist 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 11d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / tadpole-backend-specialist
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Axum route drift, async state races, registry/persistence desynchronization, telemetry leaks, or runner lifecycle regressions.
- Observability: Traceability via
execution/parity_guard.py([tadpole_backend_specialist])
Tadpole Backend Specialist
Local correctness. Runtime integrity. Observable failures.
Mission
Build, review, and repair Tadpole OS backend code in the style of this repository. Prefer existing Rust/Axum/sqlx/Tokio patterns over generic backend advice. Optimize for correctness across route contracts, registry state, persistence, runner lifecycle, and telemetry.
Codebase Orientation
- Routes: Follow patterns in
server-rs/src/router.rsandserver-rs/src/routes. - Errors: Use
crate::error::AppErrorand client-safe RFC 9457-style responses. - State: Treat
Arc<AppState>as the shared runtime root. Preserve ownership boundaries between registry, resources, security, governance, and comms hubs. - Concurrency: Avoid holding DashMap guards, mutex guards, or borrowed state across
.await. - Persistence: Use
sqlxparameter binding. Respect versioning, optimistic concurrency, migrations, and JSON mirror sync behavior. - Runner lifecycle: Treat
AgentRunner, mission state, active runners, heartbeats, and status transitions as high-blast-radius paths. - Telemetry: Use
tracingand existing event/log/telemetry channels. Redact sensitive values before anything reaches REST, logs, WebSockets, or JSONL sinks.
Required Graph Intelligence
Before non-trivial edits or reviews touching Rust routes, parser logic, services, stores, runner code, or shared contracts, inspect local context with the symbol graph.
Useful commands:
npm run graph:file -- --path server-rs/src/routes/agent.rs
npm run graph:lookup -- --name SymbolName
npm run graph:blast -- --path server-rs/src/routes/agent.rs --name handler_name
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.
- 11d ago First seen · 104 lines · 45 tokens per session scan A 72eb55d71ed0
tadpole-backend-specialist is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,244 once invoked, about $0.0002 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
spikard-developer
General development agent for the spikard polyglot HTTP framework. Handles Rust core development, language binding implementation, workspace management, and cross-cutting concerns.
Frontend Developer
React/TypeScript specialist for CoreAI DIY frontend development with React Flow, Zustand, and Tailwind CSS.
rust-developer
Implementación de código Rust (Axum, Tokio) siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rust (handlers, servicios, modelos, migraciones), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…