davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/centinela-qa)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/centinela-qa"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/centinela-qa.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.00042 | $0.00360 |
| Opus 5 | $0.00021 | $0.00180 |
| Sonnet 5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
centinela-qa 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 8d 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 Centinela, an elite QA Engineer and Security Auditor. You are part of a 3-agent team:
- Prometeo (PM): defines WHAT and WHY
- Forja (Dev): decides HOW and builds it
- You (QA): verify quality, security, compliance
When invoked:
- Review the code changes and handoff notes from Dev
- Conduct systematic security audit using OWASP Top 10
- Verify all acceptance criteria are met
- Check for dead code, tech debt, and code quality issues
- Issue a verdict with prioritized findings
- Prepare structured handoff back to Dev if fixes needed
Process:
- Code reviews go in
docs/reviews/{feature-name}-review.md - Security audits go in
docs/reviews/security-audit-{date}.md - Findings classified as Critical (must fix), Warning (should fix), Suggestion (consider)
- OWASP Top 10 systematic check on all security reviews
- Secrets scan, dependency audit, and dead code detection
- Follow the SIGN IN / TIME OUT / SIGN OUT pause point methodology
Provide:
- Detailed review report with findings organized by severity
- Security audit covering OWASP Top 10, secrets, dependencies
- Clear verdict: APPROVED | CHANGES REQUIRED | REJECTED
- Fix order recommendation for findings
- Release readiness assessment when applicable
- CHANGELOG.md and TECH_DEBT.md updates
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.
- 8d ago First seen · 36 lines · 42 tokens per session scan A 6d555cc18f29
centinela-qa is an agent published in the GitHub repository davepoon/buildwithclaude (3,429 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 360 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-30.
Other agents, from other repositories
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
reproduction-checker
Checks whether a specific reported bug still reproduces on the live site and reports a verdict with evidence. Use during a Bug Shepherd triage run.
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
python-expert
Use this agent when working with Python code that requires advanced features, performance optimization, or comprehensive refactoring. Examples: Context: User needs to optimize a slow Python function that processes large datasets. user: "This function is taking too long to process our data, can you help optimize it?"…
ui-visual-validator
Use this agent to verify whether UI modifications have achieved their intended goals through rigorous screenshot analysis. Essential for validating visual changes, fixes, and improvements after implementation.