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-scaffold)<a href="https://agentmods.dev/commands/acaprino/daodan/firefox-scaffold"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/firefox-scaffold.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.00070 | $0.01613 |
| Opus 5 | $0.00035 | $0.00807 |
| Sonnet 5 | $0.00014 | $0.00323 |
| Haiku 4.5 | $0.00007 | $0.00161 |
Grade A, and why
firefox-scaffold 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firefox Extension Scaffold
Scaffold a production-ready Firefox WebExtension with Manifest V3 defaults, web-ext CLI integration, and AMO-compatible structure.
CRITICAL RULES
- Default to Manifest V3. Firefox MV3 supports both
background.scripts(event pages with DOM access, unlike Chrome) anddeclarativeNetRequest. Only use V2 when the user has an explicit reason (ESR Firefox target, specific APIs not in V3). - Generate a working "Hello World" the user can load immediately via
web-ext run. NoTODOplaceholders as the only content of any file. - Match AMO submission requirements from day one: no binary blobs without source, no obfuscated code, valid semver, unique
idinbrowser_specific_settings. - Never hardcode user identity. If the user does not specify
--authoror--id, prompt them.
Procedure
1. Parse arguments
extension-name: required, kebab-case (becomes directory name + manifestnameslugified)--mv V2 | V3: manifest version (default V3)--sidebar: include sidebar_action--content-script: include content script template (default: include)--options-page: include options UI template
If extension id not provided, ask the user for their preferred format ({extension-name}@example.com or email-style) -- AMO requires a unique ID.
2. Directory layout
<extension-name>/
manifest.json
src/
background.js (or background.ts if --ts)
content.js (if --content-script)
popup/
index.html
popup.js
popup.css
options/ (if --options-page)
index.html
options.js
sidebar/ (if --sidebar)
index.html
sidebar.js
icons/
icon-48.png
icon-96.png
web-ext-config.js
.web-ext-artifacts/ (gitignored, build output)
.gitignore
package.json
README.md
3. Write manifest.json (MV3)
{
"manifest_version": 3,
"name": "{{Extension Name}}",
"version": "0.1.0",
"description": "{{One-line description}}",
"author": "{{Author from prompt}}",
"icons": {
"48": "icons/icon-48.png",
"96": "icons/icon-96.png"
},
"browser_specific_settings": {
"gecko": {
"id": "{{extension-id from prompt}}",
"strict_min_version": "128.0"
}
},
"permissions": [],
"host_permissions": [],
"background": {
"scripts": ["src/background.js"]
},
"action": {
"default_popup": "src/popup/index.html",
"default_title": "{{Extension Name}}"
},
"content_scripts": [
{
"matches": ["<all_urls>"],
"js": ["src/content.js"]
}
]
}
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 · 232 lines · 70 tokens per session scan A 2f29f226d78a
firefox-scaffold is a command published in the GitHub repository acaprino/daodan (8 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 1,613 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
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.
frontend-3d
You are an expert in 3D web development using Three.js, React Three Fiber, WebGL, and WebGPU. You create immersive 3D experiences for the web.
frontend-design
Read and follow the instructions in agents/frontend-design/design-all.md. Also read all referenced files in agents/frontend-design/reference/ as needed for the task.
get-component-source
The full TSX source of a component (append " demo" for its usage example).