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 agentmods add commands/gzupark/claude-plugin-pack/bifrostgit clone --depth 1 https://github.com/GzuPark/claude-plugin-packWrote 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/gzupark/claude-plugin-pack/bifrost)<a href="https://agentmods.dev/commands/gzupark/claude-plugin-pack/bifrost"><img src="https://agentmods.dev/badge/commands/gzupark/claude-plugin-pack/bifrost.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 | $0.00017 | $0.00851 |
| Opus 5 | $0.00009 | $0.00426 |
| Sonnet 5 | $0.00003 | $0.00170 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade D, and why
bifrost scanned grade D with 2 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Read `~/.claude/settings.json` and extract current `statusLine.command` path. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Bash(npm install:*), Bash(npm run build:*), Bash(rm -rf:*), How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bifrost
Open the Bifrost bridge and summon Heimdall to watch over your Claude Code session.
Step 1: Find Plugin Versions
ls -d ~/.claude/plugins/cache/claude-plugin-pack/heimdall/*/ 2>/dev/null
If no directories found:
- Inform user: "Heimdall not installed.
Run
/plugin install heimdall@claude-plugin-packfirst." - END
If directories found:
- Identify the latest version (highest semver)
- Continue to Step 2
Step 2: Check Current Settings
Read ~/.claude/settings.json and extract current statusLine.command path.
Case A: No statusLine configured
- Set
CURRENT_VERSION= none - Continue to Step 3
Case B: statusLine configured with heimdall path
- Extract version from path (e.g.,
/heimdall/1.0.1/statusline/->1.0.1) - Set
CURRENT_VERSION= extracted version - Continue to Step 3
Case C: statusLine configured with non-heimdall command
- Warn user: "Existing statusLine will be replaced"
- Set
CURRENT_VERSION= none - Continue to Step 3
Step 3: Compare Versions
If CURRENT_VERSION == LATEST_VERSION:
- Inform user: "Already up to date (v{VERSION})"
- Continue to Step 6 (cleanup only)
If CURRENT_VERSION != LATEST_VERSION:
- Continue to Step 4
Step 4: Build Latest Version
HEIMDALL=~/.claude/plugins/cache/claude-plugin-pack/heimdall
cd $HEIMDALL/<LATEST_VERSION>/statusline
npm install
npm run build
If build fails:
- Show error message
- END
If build succeeds:
- Verify
dist/index.jsexists - Continue to Step 5
Step 5: Update Settings
Update ~/.claude/settings.json:
{
"statusLine": {
"type": "command",
"command": "node <HEIMDALL_PATH>/statusline/dist/index.js",
"padding": 0
}
}
Where <HEIMDALL_PATH> is:
<HOME>/.claude/plugins/cache/claude-plugin-pack/heimdall/<LATEST_VERSION>
Use Edit tool to preserve existing settings.
If settings.json doesn't exist:
- Create new file with statusLine config only
Continue to Step 6
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.
- 4d ago First seen · 158 lines · 17 tokens per session scan D b539bc8bfc1d
bifrost is a command published in the GitHub repository GzuPark/claude-plugin-pack (6 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 851 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.