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/ahmedibrahim085/Claude-Multi-Agent-Research-System-SkillWrote 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/ahmedibrahim085/claude-multi-agent-research-system-skill/project-status)<a href="https://agentmods.dev/commands/ahmedibrahim085/claude-multi-agent-research-system-skill/project-status"><img src="https://agentmods.dev/badge/commands/ahmedibrahim085/claude-multi-agent-research-system-skill/project-status/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/commands/ahmedibrahim085/claude-multi-agent-research-system-skill/project-status"><img src="https://agentmods.dev/badge/commands/ahmedibrahim085/claude-multi-agent-research-system-skill/project-status.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.00005 | $0.00162 |
| Opus 5 | $0.00003 | $0.00081 |
| Sonnet 5 | $0.00001 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
project-status 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 10d 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
Please show the current status of the Claude Multi-Agent Research System project by reading:
-
Implementation Plan: docs/plans/FOCUSED_IMPLEMENTATION_PLAN.md
- Current phase and task
- Completed vs pending tasks
- Blockers or issues
-
Project Structure: PROJECT_STRUCTURE.md
- Verify file organization is correct
- Check all agents are in proper locations
-
Skills Status:
- multi-agent-researcher: Check skill and agents
- spec-workflow-orchestrator: Check skill and agents
-
Recent Git Activity:
- Show recent commits
- Current branch and status
Provide a concise summary of where we are and what's next.
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.
- 10d ago First seen · 25 lines · 5 tokens per session scan A b34f78a8b860
project-status is a command published in the GitHub repository ahmedibrahim085/Claude-Multi-Agent-Research-System-Skill (11 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 5 tokens to every session and 162 once invoked, about $0.0000 per session on Opus 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 commands, from other repositories
next-sprint-design
You are helping a DevOps engineer prepare a sprint kickoff message for Slack.
lavra-work-teams
Work on multiple beads with persistent worker teammates that self-organize through a ready queue.
lavra-retro
Weekly retrospective with shipping analytics, team performance, and knowledge synthesis.
lavra-work-ralph
Autonomous retry mode for bead work -- iterates until completion criteria are met or retry budget is exhausted.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
lavra-quick
Fast-track small tasks — abbreviated plan then straight to execution.