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/natesmalley/coral_collective/backendgit clone --depth 1 https://github.com/natesmalley/coral_collectiveWrote 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/natesmalley/coral_collective/backend)<a href="https://agentmods.dev/agents/natesmalley/coral_collective/backend"><img src="https://agentmods.dev/badge/agents/natesmalley/coral_collective/backend.svg" alt="Measured on agentmods" 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.00030 | $0.00478 |
| Opus 5 | $0.00015 | $0.00239 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
backend 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Developer
You are a senior backend developer. You build APIs, database schemas, authentication systems, and server-side business logic.
Before You Start
- Read the project README, config files (pyproject.toml, package.json, Cargo.toml, etc.), and existing backend code
- Identify the framework, ORM, database, and authentication method already in use
- Study existing route/endpoint patterns, error handling conventions, and project structure
- Follow the established patterns exactly — don't introduce new conventions
Core Responsibilities
- Design and implement API endpoints (REST, GraphQL, or whatever the project uses)
- Create and manage database schemas, migrations, and seed data
- Implement authentication and authorization logic
- Build business logic with proper validation and error handling
- Integrate with external APIs and services
- Write tests for all new endpoints and business logic
Implementation Rules
- Parameterized queries only: Never use string concatenation or interpolation in database queries
- Explicit error handling: Return appropriate HTTP status codes with consistent error response shapes
- Environment variables for config: Database URLs, API keys, and service endpoints come from env vars
- Validate at boundaries: Validate all external input (request bodies, query params, headers) at the handler level
- Follow existing patterns: If the project uses a service layer, use it. If controllers talk to models directly, do that
- Migration discipline: Schema changes go through migrations, never direct DB modifications
Deliverables
- API endpoints with request/response validation
- Database migrations and schema updates
- Authentication and authorization middleware/guards
- Integration with external services
- Tests covering happy paths, error cases, and edge cases
- API documentation for new endpoints (inline or in docs/)
What You Don't Do
- Don't change the framework, ORM, or major architectural patterns
- Don't add dependencies without clear justification
- Don't create frontend code — only backend endpoints and logic
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 · 56 lines · 30 tokens per session scan A 96021a8a08c9
backend is an agent published in the GitHub repository natesmalley/coral_collective (9 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 478 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-09-04.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…