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/endorphin-ai/hasbrains-agent-kitWrote 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/endorphin-ai/hasbrains-agent-kit/agent-engineering)<a href="https://agentmods.dev/plugins/endorphin-ai/hasbrains-agent-kit/agent-engineering"><img src="https://agentmods.dev/badge/plugins/endorphin-ai/hasbrains-agent-kit/agent-engineering/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/endorphin-ai/hasbrains-agent-kit/agent-engineering"><img src="https://agentmods.dev/badge/plugins/endorphin-ai/hasbrains-agent-kit/agent-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-engineering 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-engineering",
"version": "1.3.0",
"description": "Engineering discipline for AI agent systems — four always-on principles, test-driven development, verification-before-completion, system-architecture playbooks, a scope-disciplined product manager, docs/-native project management, and Claude Code → GitHub Copilot agent conversion.",
"author": {
"name": "Andrew Novykov",
"url": "https://github.com/andrewnovykov"
},
"repository": "https://github.com/endorphin-ai/hasbrains-agent-kit",
"license": "MIT",
"keywords": [
"claude-code",
"agents",
"multi-agent",
"agentic-engineering",
"reverse-engineering",
"orchestration",
"product-management",
"prd",
"roadmap",
"acceptance-criteria",
"github-copilot",
"copilot-agents"
]
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 1,154 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 Changed · +2 lines ccd72fea38a1
- 1mo ago First seen · 24 lines scan A 41efedda3174
agent-engineering is a plugin published in the GitHub repository endorphin-ai/hasbrains-agent-kit (9 stars, last pushed 12d ago), 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-31.
Other plugins, from other repositories
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
backend-development
Backend API design, GraphQL architecture, workflow orchestration with Temporal, and test-driven backend development.
playwright
Browser automation via Playwright CLI for testing, screenshots, and interaction workflows.
pm-dev
Shipping discipline for PMs who code: TDD workflow, pre-commit verification loop, security review, research-before-build.
engineering
Engineering workflow skills, review agents, and a /feature pipeline: orientation, planning, test-driven development, systematic debugging, refactoring, error handling, observability, containers, CI pipelines, dependency upgrades, migration planning, incident postmortems, code review, completion verification, and…
code-quality
Code quality pipeline — SOLID refactoring, TDD workflow, design patterns, performance optimization, and 6 specialist review agents.