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/ci)<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/ci"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/ci.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.00016 | $0.04455 |
| Opus 5 | $0.00008 | $0.02227 |
| Sonnet 5 | $0.00003 | $0.00891 |
| Haiku 4.5 | $0.00002 | $0.00445 |
Grade A, and why
ci 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 7d 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD — Trigger & Monitor GitHub Actions
Detect which platforms a JUCE project supports, show the current CI configuration, optionally change it, and trigger GitHub Actions workflows. Supports three modes: verify (build + test), sign (build + sign), and publish (build + sign + release + website update).
Arguments
status— Show recent CI runs and their resultslogsorlogs <run-id>— Show logs from the latest (or specified) CI runsecrets— Manage signing secrets (show status, sync .env → GitHub Secrets)macos,windows,linux— Trigger CI for specific platform(s), comma-separated also worksall— Trigger CI for all configured platformssign— Build and sign (no release). Requires signing certs configured.publish— Full pipeline: build, sign, GitHub Release, update website download links--no-sign-macos— Skip macOS code signing during this run--no-sign-windows— Skip Windows code signing during this run--no-create-release— In publish mode, skip GitHub Release creation- (no args) — Show current config and offer to trigger
--help— Show help reference
Examples:
/juce-dev:ci # Show config, offer to trigger
/juce-dev:ci macos # Trigger macOS-only verify build
/juce-dev:ci macos,windows # Trigger macOS + Windows
/juce-dev:ci all # Trigger all configured platforms
/juce-dev:ci sign # Build + sign (all platforms)
/juce-dev:ci publish # Full release pipeline + website update
/juce-dev:ci publish --no-sign-windows # Publish but skip Windows signing
/juce-dev:ci status # Show recent CI run results
/juce-dev:ci logs # Show logs from latest run
/juce-dev:ci secrets # Show/sync signing secrets
/juce-dev:ci --help # Show this reference
Implementation
Step 0: Handle --help
If --help is in the arguments, display this reference and stop:
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.
- 7d ago First seen · 437 lines · 16 tokens per session scan A aea6352221ee
ci is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 8d ago), licensed MIT. It adds 16 tokens to every session and 4,455 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-30.
Other commands, from other repositories
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
deploy-release
Prepare and verify a staged or production deployment with rollback and smoke checks.
rollback
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
ci
Run CI validation, create PRs, and merge on green.