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 skills add lfyxhappy/lfcode --skill integration-test-engineergit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/skills/lfyxhappy/lfcode/integration-test-engineer)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/integration-test-engineer"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/integration-test-engineer.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.00057 | $0.00346 |
| Opus 5 | $0.00028 | $0.00173 |
| Sonnet 5 | $0.00011 | $0.00069 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
integration-test-engineer 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 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.
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.
What it actually says
Integration Test Engineer
Validate collaboration between real components while controlling the environment around them.
Workflow
- Read repository instructions, integration setup, package scripts, component contracts, and existing integration tests before choosing a harness.
- Define the boundary under test, participating components, owned state, dependencies to run for real, and dependencies that must be isolated.
- Create the smallest realistic environment using repository-approved temporary resources, ephemeral services, or test configuration.
- Drive the boundary through its public entry point and assert the observable result, persisted state, emitted events, error mapping, and cleanup where relevant.
- Make setup idempotent, give test data unique ownership, and ensure teardown runs after success, failure, cancellation, and retries.
- Run the focused integration test from its package, then run broader affected checks when interfaces, migrations, or shared infrastructure changed.
Boundaries
- Keep investigation and a proposed test design read-only unless the user asks to implement tests.
- Do not point tests at production services, shared customer data, or an uncontrolled developer database.
- Do not hide a broken integration with broad mocks, blanket retries, or timing sleeps.
- Do not make destructive database, queue, filesystem, or cloud changes without explicit authorization and an isolated target.
Completion Check
Report the exercised boundary, controlled dependencies, test-data lifecycle, cleanup evidence, verification commands, and environment-dependent gaps.
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 · 29 lines · 57 tokens per session scan A 3d3fa14d6969
integration-test-engineer is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 6d ago), licensed MIT. It adds 57 tokens to every session and 346 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-09-05.
Other skills, from other repositories
Check work (verify against criteria)
Verify an implementation against acceptance criteria with a reviewer and a tester.
PR babysit (watch & drive to green)
Watch a pull request and delegate fixes until CI is green and reviews are addressed. Requires the GitHub MCP server or gh.
Write tests
Add focused, meaningful tests for code — happy path plus the edge cases that matter.
bug-fix
A structured bug-fixing workflow that takes a problem from reproduction and evidence-based cause finding through approval, implementation, testing, and cleanup.
mandu-mcp-verify
An automatic verification workflow for the Mandu project that runs after edits, generated files, or before a commit. It checks generated behavior, architecture rules, code quality, and project structure in parallel.
mandu-testing
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.