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/tajmahal226/compound-engineering-plugin/deploy-docsgit clone --depth 1 https://github.com/tajmahal226/compound-engineering-pluginWhat 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.00013 | $0.00706 |
| Opus 5 | $0.00006 | $0.00353 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
deploy-docs 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deploy-docs — 95% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Documentation Command
Validate the documentation site and prepare it for GitHub Pages deployment.
Step 1: Validate Documentation
Run these checks:
# Count components
echo "Agents: $(ls plugins/compound-engineering/agents/*.md | wc -l)"
echo "Commands: $(ls plugins/compound-engineering/commands/*.md | wc -l)"
echo "Skills: $(ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l)"
# Validate JSON
cat .claude-plugin/marketplace.json | jq . > /dev/null && echo "✓ marketplace.json valid"
cat plugins/compound-engineering/.claude-plugin/plugin.json | jq . > /dev/null && echo "✓ plugin.json valid"
# Check all HTML files exist
for page in index agents commands skills mcp-servers changelog getting-started; do
if [ -f "plugins/compound-engineering/docs/pages/${page}.html" ] || [ -f "plugins/compound-engineering/docs/${page}.html" ]; then
echo "✓ ${page}.html exists"
else
echo "✗ ${page}.html MISSING"
fi
done
Step 2: Check for Uncommitted Changes
git status --porcelain plugins/compound-engineering/docs/
If there are uncommitted changes, warn the user to commit first.
Step 3: Deployment Instructions
Since GitHub Pages deployment requires a workflow file with special permissions, provide these instructions:
First-time Setup
- Create
.github/workflows/deploy-docs.ymlwith the GitHub Pages workflow - Go to repository Settings > Pages
- Set Source to "GitHub Actions"
Deploying
After merging to main, the docs will auto-deploy. Or:
- Go to Actions tab
- Select "Deploy Documentation to GitHub Pages"
- Click "Run workflow"
Workflow File Content
name: Deploy Documentation to GitHub Pages
on:
push:
branches: [main]
paths:
- 'plugins/compound-engineering/docs/**'
workflow_dispatch:
permissions:
contents: read
pages: write
id-token: write
concurrency:
group: "pages"
cancel-in-progress: false
jobs:
deploy:
environment:
name: github-pages
url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/configure-pages@v4
- uses: actions/upload-pages-artifact@v3
with:
path: 'plugins/compound-engineering/docs'
- uses: actions/deploy-pages@v4
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.
- 3d ago First seen · 114 lines · 13 tokens per session scan A a48aba0af9f5
deploy-docs is a command published in the GitHub repository tajmahal226/compound-engineering-plugin (4 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 706 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
account
This API allows you to manage your Scaleway Projects.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
deploy
Build, test, deploy with staged rollout.
d1-migration
Run D1 migration workflow — generate, inspect, apply.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
deploy
Build a container image, push it, and deploy the service to the Akka platform. This is the transition from local development to development on the AAO platform.