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.
/plugin marketplace add handarbeit/fabriknpx agentmods add plugins/handarbeit/fabrik/entwurfgit clone --depth 1 https://github.com/handarbeit/fabrikGrade A, and why
entwurf 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 2d 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": "entwurf",
"displayName": "Entwurf",
"version": "0.1.1",
"description": "Turn a project into buildable specifications, one expert role at a time. Guided interviews for the three people a project needs: the product owner (goals, scope, vocabulary, then feature specifications), the technical architect (constraints, shared domain model, contracts, then the architecture baseline), and the experience lead (conditions of use, states, components, content). Output is a standard GitHub Spec Kit specs/ folder ready to hand to a development team, or to Fabrik. The product-owner path needs no terminal, git, or technical background.",
"author": {
"name": "handarbeit.io",
"url": "https://handarbeit.io"
},
"homepage": "https://fabrik.handarbeit.io",
"repository": "https://github.com/handarbeit/fabrik",
"keywords": [
"fabrik",
"spec-kit",
"specification",
"requirements",
"product-management",
"onboarding"
]
}
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.
- 2d ago First seen · 21 lines scan A 23b6c484d5f3
entwurf is a plugin published in the GitHub repository handarbeit/fabrik (22 stars, last pushed 3d ago), licensed Apache-2.0. 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
aidd-context
Knowledge production: project bootstrap, project init, context generation, mermaid diagrams, learn, discovery.
openoutreach marketplace
The OpenOutreach plugin for Claude Code — find B2B leads that fit, with the reason written out.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
finding-unknowns
Surface your unknowns (unknown unknowns / unknown knowns) before, during, and after implementation — eight lightweight techniques, Cartographer mode (a quadrant-coverage-gated, regret-weighted interview backed by a lifecycle-persistent unknowns ledger), and four companion agents: blindspot-scout, prototype-smith…
fable-to-opus
An adapt-first playbook that helps Opus (or any Claude model) pick up the work habits that made Fable effective — render-level verification, hypothesis-driven debugging, delegation guards, input fidelity, confirm-before-irreversible, and execution rhythm. It does NOT auto-inject rules or fake model capability. Its…
firebase
Google Firebase MCP integration. Manage Firestore databases, authentication, cloud functions, hosting, and storage. Build and manage your Firebase backend directly from your development workflow.