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/acaprino/daodanWrote 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/acaprino/daodan/firefox-publish)<a href="https://agentmods.dev/commands/acaprino/daodan/firefox-publish"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/firefox-publish.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.00054 | $0.01153 |
| Opus 5 | $0.00027 | $0.00576 |
| Sonnet 5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
firefox-publish 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 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.
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firefox Extension Publish
Signed publication to AMO. Covers pre-flight validation, signing via web-ext sign, and post-submission follow-up.
CRITICAL RULES
- Run lint first. Never submit unlinted -- Mozilla's AMO reviewers reject submissions for issues
web-ext lintcatches in 30 seconds. - Never commit API credentials. Credentials live in env vars or a gitignored
.env; refuse to proceed if they appear in the repo. - Choose the right channel:
listed-- public AMO listing, goes through Mozilla review (1-14 days, sometimes longer)unlisted-- self-distribution, auto-signed in seconds, not shown on AMO
- Bump version before submission. AMO rejects resubmissions with the same version string.
- Confirm with the user before upload. Signing is fast to revert; a listed review that starts is annoying to withdraw.
Procedure
1. Pre-flight
# Check credentials
test -n "$WEB_EXT_API_KEY" || fail "WEB_EXT_API_KEY not set"
test -n "$WEB_EXT_API_SECRET" || fail "WEB_EXT_API_SECRET not set"
# Check .env or credential files are gitignored
git check-ignore -v .env || fail ".env is not gitignored"
If credentials are missing, guide the user to https://addons.mozilla.org/en-US/developers/addon/api/key/ to generate them.
2. Run lint
Invoke /browser-extensions:firefox-lint first. If any blockers, stop.
3. Bump version
Read current version from manifest.json. If --version is supplied, use it; otherwise ask the user for:
- patch (
0.1.0->0.1.1) -- bug fixes - minor (
0.1.0->0.2.0) -- new features - major (
0.1.0->1.0.0) -- breaking change (first public release is traditionally1.0.0)
Update both manifest.json and package.json. Stage these edits but DO NOT commit automatically -- the user may want to do a final review.
4. Build
cd "$TARGET"
npx web-ext build --overwrite-dest
# Artifact: .web-ext-artifacts/<name>-<version>.zip
Verify the artifact exists and is reasonably sized (warn if > 10 MB -- large extensions get slower AMO review).
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 · 117 lines · 54 tokens per session scan A c10c739a7348
firefox-publish is a command published in the GitHub repository acaprino/daodan (8 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,153 once invoked, about $0.0003 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
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.