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-lint)<a href="https://agentmods.dev/commands/acaprino/daodan/firefox-lint"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/firefox-lint.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.00056 | $0.00889 |
| Opus 5 | $0.00028 | $0.00445 |
| Sonnet 5 | $0.00011 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
firefox-lint 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Firefox Extension Lint
Comprehensive pre-publish lint for a Firefox WebExtension.
CRITICAL RULES
- Run
web-ext lintfirst -- Mozilla's official linter catches AMO-blocking issues (remote code, missing icons, invalid manifest). - Then scan source for anti-patterns that
web-ext lintmisses: eval/Function, remote script injection, wildcards in host_permissions, stored tokens in non-session storage. - Report results grouped by severity matching AMO's own review criteria.
Procedure
1. Run web-ext lint
cd "$TARGET"
npx web-ext lint --pretty
Parse the output. If --json flag set, use --output=json and parse JSON.
2. Static checks beyond web-ext lint
Run these greps / AST checks against src/:
Forbidden / high-risk APIs (AMO review often rejects)
eval(,new Function(-- AMO blocks unless justifieddocument.write(-- CSP violationinnerHTML =with user-controlled input -- XSS risk- Remote script loading:
<script src="https://...">in extension pages browser.tabs.executeScriptwith dynamic code strings (MV2)
Permission bloat
<all_urls>inhost_permissions-- AMO reviewers ask "why?""tabs"permission without reading tab URL/title/favIcon (often over-requested)"storage"permission without anybrowser.storage.*call (dead permission)"webNavigation"withoutonBeforeNavigate/onCompletedlisteners
Auth / storage anti-patterns
- Tokens / API keys in
localStorage(persists, shared with content scripts ifall_frames) - Secrets hardcoded in source
browser.storage.localfor secrets -- acceptable but document the trust boundary
Manifest V3 migration issues (if MV3)
browser.webRequest.onBeforeRequestwith["blocking"]-- MV3 removed blocking webRequest on Chrome; Firefox still supports it but discourage for cross-browser- Service worker / event page confusion -- Firefox MV3 uses event pages (DOM access OK), Chrome MV3 uses service workers
- Missing
declarativeNetRequestrules when webRequest is being deprecated
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 · 101 lines · 56 tokens per session scan A 02bd3f7a7196
firefox-lint is a command published in the GitHub repository acaprino/daodan (8 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 889 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.