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.
npx skills add mnzralee/claude-multi-agent-architecture --skill prgit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/skills/mnzralee/claude-multi-agent-architecture/pr)<a href="https://agentmods.dev/skills/mnzralee/claude-multi-agent-architecture/pr"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/pr/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/skills/mnzralee/claude-multi-agent-architecture/pr"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/pr.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.00020 | $0.01172 |
| Opus 5.5 | $0.00008 | $0.00469 |
| Sonnet 5.5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
pr 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 2mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Skill
Create well-structured pull requests using a consistent format: conventional-commit title, body sections covering summary, changes, and test plan, and a pre-submit checklist. The discipline below is stack-agnostic; illustrative scope names use a TypeScript / Node / Express / Vitest project, but the pattern applies to any language or framework.
PR Title Format
<type>(<scope>): <description>
Same types and scopes as commit messages:
feat,fix,refactor,docs,chore,perf,test- Scopes: match your project's top-level apps or modules (e.g.
api,web,auth,payments,infra, etc.)
PR Body Template
## Summary
Brief description of what this PR does (1-3 sentences).
## Changes
- Bullet point list of changes
- Group by category if many changes
- Reference relevant files
## Test Plan
- [ ] Manual testing steps
- [ ] Unit tests added/updated
- [ ] Integration tests pass
## Screenshots (if UI changes)
[Add screenshots for visual changes]
## Notes
Any additional context, trade-offs, or follow-up work needed.
Workflow
Step 1: Ensure Branch is Ready
# Check current branch
git branch --show-current
# Ensure all changes are committed
git status
# Review commits to be included
git log main..HEAD --oneline
Step 2: Push Branch
# Push and set upstream
git push -u origin $(git branch --show-current)
Step 3: Create PR
gh pr create --title "feat(scope): description" --body "$(cat <<'EOF'
## Summary
Brief description of what this PR does.
## Changes
- Change 1
- Change 2
- Change 3
## Test Plan
- [ ] Tested locally
- [ ] Unit tests pass
- [ ] Manual verification complete
EOF
)"
Examples
Feature PR
gh pr create --title "feat(accounts): add saved-recipient management" --body "$(cat <<'EOF'
## Summary
Adds the ability for users to manage saved recipients for faster repeat transactions.
## Changes
- Add `useSavedRecipients` hook with CRUD operations
- Create `SavedRecipientListPage` with search and filtering
- Implement `AddRecipientDialog` and `EditRecipientDialog`
- Add recipient types in `src/types/recipient.ts`
- Integrate with `/api/v1/recipients` endpoints
## Test Plan
- [ ] Add a new recipient
- [ ] Edit an existing recipient
- [ ] Delete a recipient
- [ ] Search recipients by name
- [ ] Filter by account type
- [ ] Verify form validation
## Screenshots
[Add screenshots of recipient list and dialogs]
EOF
)"
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.
- 2mo ago First seen · 210 lines · 20 tokens per session scan A 984956de8584
pr is a skill published in the GitHub repository mnzralee/claude-multi-agent-architecture (8 stars, last pushed 26d ago), licensed MIT. It adds 20 tokens to every session and 1,172 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-31.
Other skills, from other repositories
coordination-worktree
A coordination method for multiple coding sessions or agents. It uses shared files as a message inbox and gives each work line its own Git worktree, which is a separate working directory connected to the same repository.
gh-backup
A backup procedure that copies code and project working files to GitHub and then checks them by cloning a fresh copy and comparing the files. It also records which data and credentials must stay out of GitHub.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
worktree-isolation
Manage git worktree lifecycle for safe, isolated parallel development.