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 45ck/skill-harness --skill external-skill-fixture-buildergit clone --depth 1 https://github.com/45ck/skill-harnessWrote 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/45ck/skill-harness/external-skill-fixture-builder)<a href="https://agentmods.dev/skills/45ck/skill-harness/external-skill-fixture-builder"><img src="https://agentmods.dev/badge/skills/45ck/skill-harness/external-skill-fixture-builder.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.00034 | $0.00319 |
| Opus 5 | $0.00017 | $0.00160 |
| Sonnet 5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
external-skill-fixture-builder 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 8d 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
External Skill Fixture Builder
Use this skill when a third-party ecosystem pattern should be tested by skill-harness but should not become a live dependency.
Process
- Choose the fixture lane by install posture, not by brand:
- pure
SKILL.mdpack - plugin manifest
- Cursor
.mdcrules - Codex/Claude/Cursor subagents
- MCP/tool config
- generated record/replay skill
- Beads or task-memory repo
- multi-agent workspace layout
- pure
- Use minimal synthetic fixtures when possible.
- Use pinned external snapshots only when real structure matters and license/provenance allows it.
- Keep fixtures out of global user directories and live install caches.
- Make the fixture assert one behavior: parse, classify, trust recommendation, drift detection, render target, or installer opt-in.
- Add a command or check that proves the fixture is exercised.
Output
Fixture Lane
Source Or Synthetic Basis
Files Included
Expected Classification
Risk Flags Expected
Check Command
Follow-Up Adoption Question
Avoid
- making fixtures large mirrors of public repos
- using fixtures as a back door for third-party adoption
- mixing fixture coverage with default installer behavior
- storing credentials, real traces, browser recordings, or private task state in fixtures
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.
- 8d ago First seen · 43 lines · 34 tokens per session scan A 84b5413bcd22
external-skill-fixture-builder is a skill published in the GitHub repository 45ck/skill-harness (15 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 319 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-30.
Other skills, from other repositories
do-it-verify
Use when selecting evidence for a delivery claim, regression fix, installation, or branch closeout.
bug-fixing
Fix defects in the Composio SDK repository with focused reproduction, root-cause analysis, regression tests, and narrow verification. Use when the user reports a bug, failing test, CI regression, runtime defect, or incorrect SDK behavior. Do not use for new feature design or broad refactors.
python-testing
Select and run Python SDK verification with nox, Makefile targets, Ruff, mypy, pytest markers, sanity tests, type inference checks, and build checks. Use when adding Python tests, diagnosing Python CI, or validating Python SDK/provider changes. Do not use for TypeScript-only checks.
typescript-providers
Implement, modify, test, or document TypeScript provider packages under ts/packages/providers, including framework adapters for OpenAI, Anthropic, Google, LangChain, Mastra, Vercel, LlamaIndex, Cloudflare, and Claude Agent SDK. Use for provider-specific TS work; do not use for core-only changes.
typescript-sdk
Implement or modify TypeScript SDK behavior in @composio/core or shared TypeScript packages, including tools, toolkits, sessions, auth configs, connected accounts, modifiers, and generated SDK surfaces. Use for TS runtime/API work; pair with typescript-testing for verification and cross-sdk-parity when Python must…
typescript-testing
Select and run TypeScript SDK verification for packages, examples, type checks, linting, builds, Vitest suites, and runtime E2E tests. Use when adding tests, diagnosing TypeScript CI, choosing a focused test command, or validating TypeScript package changes. Do not use for Python-only checks.