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/acaprino/daodanWrote 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/acaprino/daodan/project-knowledge)<a href="https://agentmods.dev/plugins/acaprino/daodan/project-knowledge"><img src="https://agentmods.dev/badge/plugins/acaprino/daodan/project-knowledge/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/acaprino/daodan/project-knowledge"><img src="https://agentmods.dev/badge/plugins/acaprino/daodan/project-knowledge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
project-knowledge 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 today.
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
{
"author": {
"name": "Alfio Caprino"
},
"description": "Durable project knowledge: instructions, audience-specific guides, implementation drift and README maintenance. Reuses existing documents, plans ownership before writing and preserves evidence, intent and author voice. Audit-only methods are callable independently by the project lifecycle.",
"license": "MIT",
"name": "project-knowledge",
"version": "1.3.6"
}
What it installs
The manifest is a name and a version. 3 skills, 3 commands, 10 agents travel with it, and installing the plugin installs all of them — 545 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill instructions-method A 51 tokens
- Skill project-knowledge A 34 tokens
- Skill readme-craft A 35 tokens
- Command guide A 0 tokens
- Command instructions A 0 tokens
- Command maintain A 0 tokens
- Agent instructions-auditor A 54 tokens
- Agent codebase-explorer A 46 tokens
- Agent doc-humanizer A 53 tokens
- Agent documentation-engineer A 47 tokens
- Agent flow-writer A 37 tokens
- Agent guide-reviewer A 47 tokens
- Agent onboarding-writer A 32 tokens
- Agent ops-writer A 39 tokens
- Agent overview-writer A 32 tokens
- Agent tech-writer A 38 tokens
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.
- today Changed c63948b70124
- yesterday Changed b2c9c840229b
- 2d ago Changed 4a895189c731
- 4d ago Changed 984716bf6ce7
- 5d ago Changed 906af22e0af1
- 6d ago Changed bdb00066cfbd
- 8d ago Changed c39c86a04c57
- 9d ago First seen · 10 lines scan A bd12dc94a7ed
project-knowledge is a plugin published in the GitHub repository acaprino/daodan (9 stars, last pushed today), 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-10-08.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.