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/plugins/davepoon/buildwithclaude/agent-triforce)<a href="https://agentmods.dev/plugins/davepoon/buildwithclaude/agent-triforce"><img src="https://agentmods.dev/badge/plugins/davepoon/buildwithclaude/agent-triforce/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/plugins/davepoon/buildwithclaude/agent-triforce"><img src="https://agentmods.dev/badge/plugins/davepoon/buildwithclaude/agent-triforce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-triforce 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.
What it actually says
{
"name": "agent-triforce",
"version": "1.0.0",
"description": "Multi-agent development system with three specialized agents (PM, Dev, QA) coordinated through checklist methodology based on The Checklist Manifesto and Boeing's checklist engineering",
"author": {
"name": "Artemio Padilla",
"url": "https://github.com/ArtemioPadilla"
},
"repository": "https://github.com/ArtemioPadilla/agent-triforce",
"license": "MIT",
"keywords": [
"agents",
"multi-agent",
"workflow-orchestration",
"checklist",
"pm",
"dev",
"qa",
"prometeo",
"forja",
"centinela",
"feature-spec",
"security-audit",
"code-health",
"release-check",
"skills"
]
}
What it installs
The manifest is a name and a version. 6 skills, 3 agents travel with it, and installing the plugin installs all of them — 352 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 29 lines scan A 4447a40fa87c
agent-triforce is a plugin published in the GitHub repository davepoon/buildwithclaude (3,675 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
analyze-issue
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.
pm-core
Everyday product management work: PRDs, prioritization, market sizing, meeting prep, stakeholder intel, weekly status, critique.
project-curator
Reorganizes project structure by cleaning root clutter, creating logical folder hierarchies, and moving files to optimal locations. Tracks dependencies and fixes broken imports/paths. Use PROACTIVELY when project structure becomes unwieldy or needs architectural cleanup.
atl-fetch
A plugin that retrieves information from Atlassian Cloud, including Jira issue tracking and Confluence team wikis.
catalyst-dev
Complete development workflow: research → plan → implement → validate → ship. Includes research agents, planning tools, handoff system, Linear integration, and PM commands.
catalyst-pm-ops
Linear backlog grooming — orphan, stale, and duplicate ticket detection.