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 bdfinst/agentic-dev-team/plugin install security-assessmentWrote 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/bdfinst/agentic-dev-team/cross-repo-analysis)<a href="https://agentmods.dev/commands/bdfinst/agentic-dev-team/cross-repo-analysis"><img src="https://agentmods.dev/badge/commands/bdfinst/agentic-dev-team/cross-repo-analysis.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.00048 | $0.00869 |
| Opus 5 | $0.00024 | $0.00434 |
| Sonnet 5 | $0.00010 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
cross-repo-analysis 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 2d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/cross-repo-analysis
You have been invoked with the /cross-repo-analysis command.
Role
Orchestrator for cross-repo security analysis. Composes deterministic tool outputs (service-comm-parser, shared-cred-hash-match) with the cross-repo-synthesizer agent's narrative synthesis.
Constraints
- Minimum two target repos. Below that, this command is a no-op — use
/security-assessmentfor a single repo. - No detection. This command assumes
/security-assessmenthas already run per repo (or RECON has been generated per repo). It does not re-scan. - Mermaid passthrough. The diagram from
service-comm-parser.pyflows through unchanged to the final report.
Parse arguments
Arguments: $ARGUMENTS
Positional: two or more directory paths. Each must contain memory/recon-<slug>.json (produced by an earlier codebase-recon run) or the command refuses.
Steps
1. Verify RECON per repo
For each path, locate memory/recon-*.json. If any target path lacks a RECON artifact, stop and tell the user: "Target has no RECON artifact — run codebase-recon or /security-assessment <path> first."
2. Run service-comm-parser.py
python3 "${CLAUDE_PLUGIN_ROOT}/harness/tools/service-comm-parser.py" <path1> <path2> ... > memory/service-comm-<slug>.mermaid
Where <slug> is a dash-joined concatenation of target repo names.
3. Run shared-cred-hash-match.py
python3 "${CLAUDE_PLUGIN_ROOT}/harness/tools/shared-cred-hash-match.py" <path1> <path2> ... > memory/shared-cred-<slug>.sarif
The SARIF output is consumed by the synthesizer agent; it is NOT passed through the unified-finding SARIF parser at this stage (findings are shared-credential hashes, not code-level issues).
4. Dispatch cross-repo-synthesizer
Using the Agent tool, dispatch the cross-repo-synthesizer agent with inputs:
- List of RECON artifact paths (one per repo)
- Path to the Mermaid file from step 2
- Path to the shared-cred SARIF from step 3
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.
- 2d ago First seen · 84 lines · 48 tokens per session scan A 16905645ad33
cross-repo-analysis is a command published in the GitHub repository bdfinst/agentic-dev-team (280 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 869 once invoked, about $0.0002 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-09-05.
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.