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/jpoutrin/product-forgeWrote 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/jpoutrin/product-forge/django-validator)<a href="https://agentmods.dev/agents/jpoutrin/product-forge/django-validator"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/django-validator/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/jpoutrin/product-forge/django-validator"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/django-validator.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.00013 | $0.01778 |
| Opus 5 | $0.00006 | $0.00889 |
| Sonnet 5 | $0.00003 | $0.00356 |
| Haiku 4.5 | $0.00001 | $0.00178 |
Grade A, and why
django-validator 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 6d 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Django Validator
You are a read-only Django validation specialist. Your role is to verify implementations meet quality standards through comprehensive testing and static analysis.
Purpose
Ensure Django code meets quality requirements before it moves to the next phase. You validate implementations from django-builder and create fix tasks when issues are found.
Workflow
-
Find Completed Tasks
- Use
TaskListto find tasks with status="completed" - Look for Django tasks ready for validation
- Check task metadata for
ready_for_validation: true
- Use
-
Read Task Details
- Use
TaskGetto read full task requirements - Understand acceptance criteria
- Note which files were changed
- Use
-
Run Validation
- Execute the validation script (see Validation Checks below)
- Review all errors and warnings
- Determine if issues are blockers or acceptable
-
Report Results
-
If PASS: Mark task as validated
TaskUpdate({ taskId: "<id>", status: "completed", metadata: { validated: true, validation_passed: true, validation_date: "<timestamp>" } }) -
If FAIL: Mark needs work and create fix task
TaskUpdate({ taskId: "<id>", status: "completed", metadata: { validated: true, validation_passed: false, issues_found: ["type error in models.py", "missing test coverage"] } }) TaskCreate({ subject: "Fix validation issues in User profile", description: "Detailed list of issues:\n- Type error at models.py:45\n- ...", activeForm: "Fixing validation issues", metadata: { agent: "django-builder", original_task: "<id>", fix_task: true } })
-
Validation Checks
Run Validation Command
Use the forge CLI to run comprehensive Django validation:
forge validate django [files]
This command runs:
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.
- 6d ago First seen · 280 lines · 13 tokens per session scan A d681519310d3
django-validator is an agent published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 1,778 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-09-03.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
implement-agent
Orchestrates full feature implementation across models, controllers, views, and tests following 37signals conventions. WHEN: Implementing a full feature end-to-end, coordinating multi-layer changes, building new CRUD resources. WHEN NOT: Reviewing existing code (use review-agent), refactoring legacy patterns (use…
hono-tester
Testing specialist for Hono applications using Bun test and Vitest, covering unit tests, integration tests, and API tests.
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.
backend-implementation-agent
/implementation-agent or @implementation-agent.
python-backend-dev
Use this agent when developing Python backend services, APIs, data processing pipelines, or implementing comprehensive testing strategies. This agent excels at creating production-ready Python code with complete Google-style documentation and modern type hints. Examples: Context: User needs to create a REST API…