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/lexfrei/ccc/templgit clone --depth 1 https://github.com/lexfrei/cccWhat 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.00034 | $0.03537 |
| Opus 5 | $0.00017 | $0.01768 |
| Sonnet 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 2d 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.
- 2d ago First seen · 617 lines · 34 tokens per session scan A d9e95d67604d
templ is an agent published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 34 tokens to every session and 3,537 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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".