Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add acaprino/daodan/plugin install codebase-xrayWrote 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/commands/acaprino/daodan/team-analyze)<a href="https://agentmods.dev/commands/acaprino/daodan/team-analyze"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/team-analyze.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.07114 |
| Opus 5 | $0.00000 | $0.03557 |
| Sonnet 5 | $0.00000 | $0.01423 |
| Haiku 4.5 | $0.00000 | $0.00711 |
Grade A, and why
team-analyze 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team-analyze
Execution harness
Selected topology: native-team. Use native Agent Teams when they are enabled in this session; otherwise dispatch the same roles as isolated subagents. Both paths satisfy the same contract, and which one answered changes nothing a reader of the report can observe.
Harness obligations, none of them optional:
- Every dispatched worker runs in its own context. A worker never reads another worker's result, and never runs in the coordinator's context.
- Follow the dispatch plan below in phase order. A phase starts only after every phase it needs has
closed, and a phase closes only when every worker it dispatched is recorded
deliveredorfailed. A missing result is a recorded failure, never a silently shorter report. - Dispatch only roles from this set, and only as the plan says:
partition-behavior-worker,partition-quality-worker,partition-structure-worker,partition-synthesizer,semantic-interconnect-mapper - Only the phase that declares the report artifact may write it.
Dispatch plan:
partition-selection: runs in the orchestrating context; producesselection:partitions.structure: onepartition-structure-workerper item ofselection:partitions, each in its own isolated context, in parallel where the host allows; barrierall-delivered; needspartition-selection; producesartifact:partition-structure.behavior: onepartition-behavior-workerper item ofselection:partitions, each in its own isolated context, in parallel where the host allows; barrierall-delivered; needsstructure; consumesartifact:partition-structure; producesartifact:partition-behavior.quality: onepartition-quality-workerper item ofselection:partitions, each in its own isolated context, in parallel where the host allows; barrierall-delivered; needsstructure; consumesartifact:partition-structure; producesartifact:partition-quality.interconnect: onesemantic-interconnect-mapperin an isolated context; needsbehavior; consumesartifact:partition-behavior; producesartifact:interconnect-map.synthesis: onepartition-synthesizerin an isolated context; needsbehavior,quality,interconnect; consumesartifact:partition-structure,artifact:partition-behavior,artifact:partition-quality,artifact:interconnect-map; producesartifact:xray-report.
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.
- yesterday Changed · +56 lines df87b2bfc0d9
- 6d ago First seen · 410 lines · 0 tokens per session scan A fe0d5031133d
team-analyze is a command published in the GitHub repository acaprino/daodan (8 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,114 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.