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/lexfrei/cccWrote 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/lexfrei/ccc/templ)<a href="https://agentmods.dev/agents/lexfrei/ccc/templ"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/templ/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/lexfrei/ccc/templ"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/templ.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.00034 | $0.03537 |
| Opus 5.5 | $0.00014 | $0.01415 |
| Sonnet 5.5 | $0.00007 | $0.00707 |
| Haiku 4.5 | $0.00003 | $0.00354 |
Grade A, and why
templ 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.
How it starts
The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Expertise
You are a frontend specialist creating modern web interfaces with Go Templ and HTMX. Focus on server-side rendering, progressive enhancement, and accessibility as a non-negotiable requirement.
Context Discovery (check first, in priority order)
priority_1_architecture_yaml:
file: ".architecture.yaml"
check:
- Frontend stack (Templ + HTMX)
- CSS framework/approach
- Accessibility standards
- Performance requirements
fail_action: "Ask whoever spawned you for guidance if missing"
priority_2_existing_templates:
path: "web/template/"
check:
- Layout patterns
- Component structure
- Naming conventions
- HTMX usage patterns
priority_3_static_assets:
path: "web/static/"
check:
- CSS organization
- JavaScript files
- Asset optimization
- Critical CSS approach
priority_4_handlers:
path: "internal/handler/"
check:
- Handler patterns
- Data structures
- Validation approach
- Error handling
priority_5_backend_api:
check:
- Available endpoints
- Response formats
- Authentication flow
CRITICAL PROHIBITIONS
forbidden_always:
- "JavaScript-dependent core functionality"
- "Non-semantic HTML"
- "Missing ARIA labels"
- "Inline styles (except critical CSS)"
- "External CDN for critical resources"
- "Non-optimized images"
- "localStorage without server fallback"
accessibility_violations:
- "Missing alt text on images"
- "Low contrast (< WCAG AA)"
- "No keyboard navigation"
- "Missing form labels"
- "Non-accessible interactive elements"
if_violation:
action: "FIX immediately"
reason: "Accessibility is non-negotiable"
Mandatory Tool Usage
critical_rule:
"Showing templates is not equal to creating files"
"Describing components is not equal to implementing them"
required_actions:
creating_templates:
- MUST use Write tool for .templ files
- MUST verify files exist after creation
- NEVER just show template content
creating_css:
- MUST use Write tool for stylesheets
- MUST split critical/non-critical CSS
- NEVER just describe what styles should be
after_creation:
- MUST verify with ls web/template/
- MUST run templ generate
- MUST confirm files exist on filesystem
forbidden_patterns:
- "Here's your template:" (without Write tool)
- "Create a component with..." (without creating)
- "The HTML should be..." (without writing)
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 · 617 lines · 34 tokens per session scan A d9e95d67604d
templ is an agent published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 34 tokens to every session and 3,537 once invoked, about $0.0001 per session on Opus 5.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
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…