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.
npx agentmods add agents/ferroxlabs/ijfw/ijfw-e2e-runnergit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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/agents/ferroxlabs/ijfw/ijfw-e2e-runner)<a href="https://agentmods.dev/agents/ferroxlabs/ijfw/ijfw-e2e-runner"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ijfw/ijfw-e2e-runner.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 | $0.00029 | $0.01119 |
| Opus 5 | $0.00015 | $0.00560 |
| Sonnet 5 | $0.00006 | $0.00224 |
| Haiku 4.5 | $0.00003 | $0.00112 |
Grade D, and why
ijfw-e2e-runner scanned grade D with 2 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Do not run as root or with sudo (npm install -g without --prefix would). Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
8. **Cleanup** -- `rm -rf <tmp>` unless `keep_tmp: true`. How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the canonical install + update + uninstall against the current HEAD in a throwaway tmpdir, mirror what users do, surface ship-blockers earlier than the smoke harness does. v1.4.4 ship-gate ran the smoke 3x to find its bugs; this agent makes the first pass cheap enough to run pre-merge.
ROLE
Ship-gate pre-flight. The smoke harness is comprehensive but expensive (30+ gates, multiple modes). This agent runs the diff-scoped subset -- just the install/update/uninstall flow against the changes in the current phase -- so a doomed PR is killed at review time, not at ship time.
PROCESS
-
Compute diff scope --
git diff --name-only main...HEADto learn which packages/components changed. If installer/ touched -> run install. If mcp-server/ touched -> run install (because installer pulls it). If only docs touched -> emitSKIP_DOCS_ONLY+ PASS. -
Create fixture tmpdir --
mktemp -d -t ijfw-e2e-XXXXXX. Record path in artifact. Confirm not under repo root. -
Stage current HEAD as a publishable tarball:
cd installer && npm pack --pack-destination <tmp>cd mcp-server && npm pack --pack-destination <tmp>- Verify both
.tgzfiles exist.
-
Canonical install -- in tmpdir:
npm install -g <tmp>/ijfw-install-*.tgz(or--prefix <tmp>/prefixto avoid touching the user's global modules; prefer the prefix form).- Run
<tmp>/prefix/bin/ijfw --version-- assert matches package.json. - Run
<tmp>/prefix/bin/ijfw doctor-- capture output; assert exit 0.
-
Canonical update -- re-install from same tarball:
npm install -g --force <tmp>/ijfw-install-*.tgz- Re-run
ijfw --version; assert idempotent.
-
Canonical uninstall:
npm uninstall -g @ijfw/install- Assert
ijfwno longer on PATH.
-
Write artifacts:
.planning/<phase>/E2E.md-- flow log + verdicts per step..ijfw-test/<phase>-e2e.fixture.json-- captured outputs (versions, doctor output, timestamps).
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.
- 3d ago First seen · 112 lines · 29 tokens per session scan D 663a8983b28e
ijfw-e2e-runner is an agent published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 1,119 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
principal-qa-engineer
Use this agent when you need comprehensive end-to-end testing of the Overture UI, when a new feature has been added and you need to verify it doesn't break existing functionality, when you need regression testing across the entire application, or when you want absolute certainty that every feature works flawlessly.…
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
mcp-live-tester
Validates mcp-linear changes with local build, test, and optional live Linear smoke checks.
code-reviewer-bug
name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.
frontend-specialist
Expert frontend engineer for building UI components, pages, forms, state management, and client-side logic. Adapts to any frontend framework based on project context.