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 causify-ai/helpers --skill testing.fix_input_output_varsgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/testing.fix_input_output_vars)<a href="https://agentmods.dev/skills/causify-ai/helpers/testing.fix_input_output_vars"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/testing.fix_input_output_vars/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/causify-ai/helpers/testing.fix_input_output_vars"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/testing.fix_input_output_vars.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00009 | $0.00183 |
| Opus 5.5 | $0.00004 | $0.00073 |
| Sonnet 5.5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
testing.fix_input_output_vars 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 1mo 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
Goal
-
Transform test method so that:
- The inputs and outputs are strings with """ and dedent
- The output being checked with
self.assert_equal() - Follow the directions in
.claude/skills/testing.rules.md# Writing Test Code## Code Formatting in Tests# Test Input and Output Handling## Compare Whole Output with assert_equal, Not Piecewise
-
Factor out as much code as possible in helper functions
- Follow the directions in
.claude/skills/testing.rules.md## Use Helper Methods When You Have Repetitive Tests
- Follow the directions in
-
Do not change the intent of the test
Verification
- Run the tests to make sure that the tests are passing
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.
- 1mo ago Changed 51d8b14a0d48
- 1mo ago First seen · 24 lines · 9 tokens per session scan A 2c462b6fb169
testing.fix_input_output_vars is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 9 tokens to every session and 183 once invoked, about $0.0000 per session on Opus 5.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-03.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.