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 mdsakalu/agent-plugins/plugin install workspaceWrote 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/mdsakalu/agent-plugins/add-repo)<a href="https://agentmods.dev/commands/mdsakalu/agent-plugins/add-repo"><img src="https://agentmods.dev/badge/commands/mdsakalu/agent-plugins/add-repo.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.00010 | $0.00540 |
| Opus 5 | $0.00005 | $0.00270 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
add-repo 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 6d 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
Onboard a new repository into the universal metarepo.
Resolve the metarepo path by reading ~/.claude/workspace-config.json and expanding ~ to $HOME.
The user's request: $ARGUMENTS
Steps
- Read
~/.claude/workspace-config.jsonto get the metarepo path. Expand~to$HOME. - Parse the user's input for the repository source:
- Full GitHub URL:
https://github.com/org/repo - Shorthand:
org/repo(e.g.,acme/my-project) - Just an org name: use
gh repo list <org> --limit 20 --json name,urlto discover repos and let user pick
- Full GitHub URL:
- Check if the repo is already onboarded:
- Look for
<metarepo>/repos/<name>/.repo.json - If found, inform the user and suggest
/workspace:newinstead
- Look for
- Run the add-repo script:
The script handles: cloning, JJ init, .repo.json, trunk workspace.json, symlinks, .git/info/exclude.bash ${CLAUDE_PLUGIN_ROOT}/scripts/workspaces/add-repo.sh <url-or-org/repo> - Commit the new notes to the metarepo:
cd <metarepo> && git add notes/<repo>/ && git commit -m "Onboard <repo> repository" - Report success and suggest next steps:
/workspace:new <repo> <name>to create first workspace/workspace:listto see all workspaces
Important
- Always resolve metarepo from
~/.claude/workspace-config.json, never hardcode paths. - This clones a potentially large repository. Warn the user it may take a while.
- Repos are cloned to
<metarepo>/repos/<name>/trunk/(gitignored). - Notes/metadata go to
<metarepo>/notes/<name>/trunk/(git-tracked). - Handle errors: auth failures, non-existent repos, network issues.
- If
ghis not authenticated, suggestgh auth login.
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.
- 6d ago First seen · 43 lines · 10 tokens per session scan A 5578c1183661
add-repo is a command published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 540 once invoked, about $0.0001 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-31.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.