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/helderberto/agent-skillsWrote 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/helderberto/agent-skills/marketplace)<a href="https://agentmods.dev/plugins/helderberto/agent-skills/marketplace"><img src="https://agentmods.dev/badge/plugins/helderberto/agent-skills/marketplace/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/helderberto/agent-skills/marketplace"><img src="https://agentmods.dev/badge/plugins/helderberto/agent-skills/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
helderberto-skills marketplace 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 5d 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": "helderberto-skills",
"owner": {
"name": "Helder Burato Berto",
"email": "[email protected]"
},
"metadata": {
"description": "Helder's personal SDLC toolbelt for AI coding agents — covering triage, grill, spec, tickets, build, review, PR, and retro."
},
"plugins": [
{
"name": "hb",
"source": {
"source": "github",
"repo": "helderberto/agent-skills"
},
"description": "Helder Berto's 🛠️ Battle-tested software engineering skills for AI coding agents 🤖, from idea to PR."
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed 5f3e8a8a16c4
- 8d ago Changed 69880ea9d8e1
- 1mo ago First seen · 21 lines scan A 54a9884d2fae
helderberto-skills marketplace is a plugin published in the GitHub repository helderberto/agent-skills (17 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
skillengine
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
balanced-scorecard
Strategy maps and balanced scorecards — perspective design, causal-link strategy mapping, lead/lag measure selection, target-and-initiative setting, cascaded business-unit scorecards, and periodic reviews that test the strategy's causal theory, not just the numbers.
market-intelligence
Competitive landscape, incentive mapping, positioning, and information asymmetry — strategic-group mapping with mobility-barrier analysis, incentive-driven behavior prediction, positioning trade-off discipline, information-asymmetry analysis, and game-theory-grounded competitive response forecasting.
change-management
Stakeholder impact mapping, change readiness assessment, sponsor roadmaps, communications planning, and resistance diagnosis — the people side of transformation, separate from program governance and operating model design.
consulting
Strategic narrative, hypothesis-driven problem solving, and deliverable craft — Minto pyramid structure, hypothesis trees, hypothesis-driven workplans, deck outlines, exec memos, so-what sharpening, and doc/deck review.
okr
Objectives and Key Results — drafting objectives that aren't disguised metrics, writing outcome-based key results, target calibration, cascading with conflict detection, confidence-based check-ins, and end-of-cycle scoring with retro.