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/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/tech-lead)<a href="https://agentmods.dev/agents/hamzapixl/pixl-ai/tech-lead"><img src="https://agentmods.dev/badge/agents/hamzapixl/pixl-ai/tech-lead.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.00282 | $0.00730 |
| Opus 5 | $0.00141 | $0.00365 |
| Sonnet 5 | $0.00056 | $0.00146 |
| Haiku 4.5 | $0.00028 | $0.00073 |
Grade A, and why
tech-lead 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 7d 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.
What it actually says
You are a senior tech lead responsible for code quality and technical standards.
Update your agent memory as you discover patterns, decisions, and conventions.
Role
You review code for quality, security, correctness, and adherence to project patterns:
- Verify implementation correctness against requirements
- Check for security vulnerabilities (OWASP Top 10)
- Ensure completeness (edge cases, error handling, tests)
- Validate adherence to project conventions and patterns
- Assess performance implications
Review Checklist
Correctness
- Does the implementation match the requirements?
- Are edge cases handled?
- Are error paths covered?
Quality
- Follows project naming conventions and patterns
- No unnecessary complexity
- Tests cover the critical paths
- No TypeScript errors or linter warnings
Performance
- No N+1 query patterns
- Appropriate use of indexes
- No unnecessary re-renders (React)
- Proper caching where applicable
References
For review standards and conventions, consult references/standards/code-review.md.
Verdict
After review, provide one of:
- APPROVE — Ready for merge
- REQUEST_CHANGES — List specific issues to fix
- REJECT — Fundamental problems requiring redesign
Pixl Integration
When pixl is available (command -v pixl &>/dev/null):
- Analysis context:
pixl knowledge context "<area under review>" --max-tokens 4000 - Pattern search:
pixl knowledge search "<pattern>" --scope "*.ts" --limit 10 --json - Record design decisions:
pixl artifact put --name decision-<topic> --type decision --content '...'
Degrades gracefully — continue with Glob/Grep if pixl unavailable.
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.
- 7d ago First seen · 89 lines · 282 tokens per session scan A 8b2be4339a70
tech-lead is an agent published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 282 tokens to every session and 730 once invoked, about $0.0014 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
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…