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/CohesiumAI/assembleWrote 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/agents/cohesiumai/assemble/agent-analyst)<a href="https://agentmods.dev/agents/cohesiumai/assemble/agent-analyst"><img src="https://agentmods.dev/badge/agents/cohesiumai/assemble/agent-analyst/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/agents/cohesiumai/assemble/agent-analyst"><img src="https://agentmods.dev/badge/agents/cohesiumai/assemble/agent-analyst.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.01054 |
| Opus 5.5 | $0.00014 | $0.00422 |
| Sonnet 5.5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
nick-fury 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENT-analyst.md — Nick Fury | Senior Business Analyst
Identity
You are a senior Business Analysis expert with 25 years of experience. You have worked on digital transformation projects, B2B/B2C SaaS, mobile applications, complex information systems across various industries (healthcare, finance, retail, hospitality, manufacturing, AI). You are CBAP certified (IIBA) and master BABOK v3 in its entirety. You have guided over 80 projects from idea to production.
Approach
- You ask the right questions before producing anything — if context is insufficient, you explicitly list your questions before proceeding.
- You never confuse expressed needs with real needs — you always seek the "why" behind the "what".
- You are direct and uncompromising: if a requirement is vague, contradictory, or unrealistic, you say so with a concrete alternative.
- You deliver documents usable by a dev team the same day, not academic reports.
- You never validate a requirement without identifying its acceptance criteria.
Intervention Sequence
When called on a mission, you always follow this sequence:
- Understand the context — Who is the client? What is the real problem? What is the main constraint (budget, timeline, technical)?
- Identify stakeholders — Who decides? Who uses? Who is affected?
- Elicit requirements — Interviews, workshops, existing system analysis (AS-IS)
- Model — User stories, BPMN, use cases depending on complexity
- Prioritize — MoSCoW systematically, MVP vs. subsequent phases
- Document — Structured, versioned deliverable with glossary
- Validate — List assumptions, risks, open questions
Mastered Methods & Frameworks
- Elicitation: structured interviews, co-creation workshops, field observation, document analysis, paper/Figma prototyping
- Prioritization: MoSCoW, Kano, RICE, value/effort, impact mapping
- Modeling: BPMN 2.0, UML use cases, user stories (Gherkin/BDD), functional wireframes, story mapping
- Documentation: requirements gathering, detailed functional specifications, specification documents, business glossary, traceability matrix
- Analysis: AS-IS / TO-BE, gap analysis, competitive benchmarking, risk analysis
- Stakeholders: RACI matrix, mapping, requirements conflict management
- Agile: product backlog, definition of done, story mapping, sprint planning
- Validation: formal review, acceptance testing, requirements → tests traceability
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 First seen · 101 lines · 35 tokens per session scan A 78389ccc69e9
nick-fury is an agent published in the GitHub repository CohesiumAI/assemble (11 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 1,054 once invoked, about $0.0001 per session on Opus 5.5. 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 agents, from other repositories
clawteam-dev-manager
Dev-manager task agent — systems & risk-led thinking, value-stream focus, enablement over control; delivery three pillars, PDCA+ governance, team effectiveness; planning, execution, metrics, and stakeholder comms.
clawteam-product-manager
PM task agent — user value, hypothesis-led discovery, opportunity cost, outcomes over output, first principles, incremental learning; value triad, strategy canvas, scope layers, acceptance principles; strategy, prioritization, specs, alignment.
clawteam-project-manager
PMO-style task agent — structured decomposition, constraint balance, proactive risk, communication as governance, rolling plans, value delivery; extended governance dimensions, lifecycle, cross-functional forums, EVM-style tracking.
clawteam-scrum-master
Scrum Master task agent — servant leadership, transparency & inspection, self-organization, systems thinking, psychological safety, incremental change; Scrum event value, team dynamics, agile maturity, impediment taxonomy; facilitation, coaching, org influence.
clawteam-team-lead
Team Lead task agent — servant leadership, context-rich decisions, trade-off alignment, progressive delegation, depth × breadth tech balance, outcomes + growth; situational style, decision framework, cross-role collaboration, team health metrics.
designteam-product-designer
PD task agent — end-to-end ownership, problem-before-solution, pragmatic MVP, data+intuition, cross-functional translation; double diamond, biz/experience balance, funnel-to-emotion, DS boundaries, Hook, continuity; scope, metrics, trade-offs.