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.
git clone --depth 1 https://github.com/danielraffel/generous-corp-marketplaceWrote 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/danielraffel/generous-corp-marketplace/website)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/website"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/website.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.00012 | $0.01591 |
| Opus 5 | $0.00006 | $0.00796 |
| Sonnet 5 | $0.00002 | $0.00318 |
| Haiku 4.5 | $0.00001 | $0.00159 |
Grade C, and why
website scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
git rm -rf . 2>/dev/null || true How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Website — GitHub Pages Download Page
Create a GitHub Pages download page for your plugin. Sets up a gh-pages branch with a responsive landing page showing your plugin name, description, and download buttons. Download links are automatically updated when you publish (/juce-dev:build publish or /juce-dev:ci publish).
Arguments
- (no args) — Create a gh-pages branch with the website template (or report if one already exists)
--regenerate— Force regenerate the page from the template (overwrites existing)--no-github-link— Omit the GitHub source link (useful for private repos)--help— Show help reference
Examples:
/juce-dev:website # Set up GitHub Pages download page
/juce-dev:website --no-github-link # Private repo — no source link
/juce-dev:website --regenerate # Rebuild page from template
/juce-dev:website --help # Show this reference
Implementation
Step 0: Handle --help
If --help is in the arguments, display this reference and stop:
juce-dev:website — Create a GitHub Pages download page
USAGE:
/juce-dev:website Set up download page
/juce-dev:website --no-github-link Omit GitHub source link
/juce-dev:website --regenerate Rebuild from template
WHAT IT CREATES:
A gh-pages branch with a single index.html — your plugin name,
description, and download buttons for macOS and Windows.
• Light and dark mode
• Open Graph + Twitter Card meta tags
• Download buttons start as "Coming Soon" stubs
• Buttons auto-activate when you first publish
• URLs auto-update on subsequent publishes
HOW DOWNLOADS UPDATE:
When you run /juce-dev:build publish or /juce-dev:ci publish,
the publish pipeline calls update_download_links.sh which:
1. First publish: replaces "Coming Soon" stubs with active buttons
2. Later publishes: updates version numbers in existing URLs
This happens automatically — no manual website editing needed.
CUSTOMIZATION:
The page is intentionally simple. After creation, you can edit
index.html on the gh-pages branch to add features, screenshots,
or other content. Your customizations are preserved — only the
download button blocks (between marker comments) are touched
during publish updates.
SOCIAL SHARING:
Add a 1200x630px image to web-images/og-image.png on gh-pages
for rich previews in iMessage, Slack, Discord, and Twitter/X.
YOUR PAGE URL:
https://<github-user>.github.io/<repo>/
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.
- 8d ago First seen · 192 lines · 12 tokens per session scan C 1df96b9d1ea6
website is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 9d ago), licensed MIT. It adds 12 tokens to every session and 1,591 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
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.
ship
Ship is the operational release-prep flow for a connected project repo.
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.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.