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 skills/yu-iskw/coding-agent-fabric/test-integration-dockernpx skills add yu-iskw/coding-agent-fabric --skill test-integration-dockergit clone --depth 1 https://github.com/yu-iskw/coding-agent-fabricWrote 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/yu-iskw/coding-agent-fabric/test-integration-docker)<a href="https://agentmods.dev/skills/yu-iskw/coding-agent-fabric/test-integration-docker"><img src="https://agentmods.dev/badge/skills/yu-iskw/coding-agent-fabric/test-integration-docker.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.00037 | $0.00494 |
| Opus 5 | $0.00018 | $0.00247 |
| Sonnet 5 | $0.00007 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
test-integration-docker 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 4d 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 Testing with Docker & Real Skills
This skill executes integration tests in a containerized environment using actual skill repositories from the community. It uses a Makefile to manage the build and test lifecycle.
Workflow Checklist
- Step 1: Environment Readiness
- Verify Docker is running.
- Step 2: Execute Tests
- Run
make -C integration_tests testin the project root.
- Run
- Step 3: Lifecycle Management
- Use
make -C integration_tests cleanif needed to prune images.
- Use
Detailed Instructions
1. Run Integration Tests
Ensure the Docker daemon is active, then execute the following command from the project root to build the image and run the full test suite:
make -C integration_tests test-verbose
2. Standard Makefile Targets
You can also use the Makefile directly for granular control:
Build the image only
make -C integration_tests build
Clean up images
make -C integration_tests clean
Success Criteria
- Docker image builds successfully with
gitandmakeinstalled. cafCLI is linked and available in the container.- Real-world skills are cloned from GitHub (Vercel, Anthropic).
caf skills addsuccessfully installs these real skills.- All integration scenarios pass.
Scenarios Covered
- CLI Health: Version and help checks.
- Real-World Skills (Vercel): Clones
vercel-labs/agent-skillsand installs skills likeweb-design-guidelines. - Real-World Skills (Anthropic): Clones
anthropics/skillsand installs document skills. - Subagent Verification: Lists available subagents in the clean container.
- Multi-Agent Matrix: Tests are executed for both
Claude CodeandCursoragents. - Scope Isolation: Tests are executed for both
projectandglobalscopes, verifying that global installations do not leak into the project'spackage.json.
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.
- 4d ago First seen · 61 lines · 37 tokens per session scan A 7f1ddc783860
test-integration-docker is a skill published in the GitHub repository yu-iskw/coding-agent-fabric (1 stars, last pushed 19d ago), licensed Apache-2.0. It adds 37 tokens to every session and 494 once invoked, about $0.0002 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 skills, from other repositories
delegate-coding-agent
Route coding work to another local coding-agent CLI through the llm-provider MCP server. Use when a task benefits from a powerful model for difficult reasoning or a faster, lower-cost model for bounded implementation, tests, investigation, or review.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.