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 Affitor/agent-skills --skill test-integrationgit clone --depth 1 https://github.com/Affitor/agent-skillsWrote 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/affitor/agent-skills/test-integration)<a href="https://agentmods.dev/skills/affitor/agent-skills/test-integration"><img src="https://agentmods.dev/badge/skills/affitor/agent-skills/test-integration/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/affitor/agent-skills/test-integration"><img src="https://agentmods.dev/badge/skills/affitor/agent-skills/test-integration.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00505 |
| Opus 5.5 | $0.00013 | $0.00202 |
| Sonnet 5.5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
test-integration 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
Test Integration
Verify your Affitor tracking pipeline works end-to-end using the CLI.
Test Individual Steps
# Test click tracking
npx affitor test click
# Test signup/lead tracking
npx affitor test lead
# Test sale/payment tracking
npx affitor test sale
Each command sends a test event to the Affitor API and confirms it was received and processed correctly.
What Each Test Verifies
test click
- Sends a simulated affiliate click event
- Confirms the tracking API accepts and stores the click
- Verifies your program ID and API key are valid
test lead
- Sends a test signup/lead event with a mock customer
- Confirms attribution linking works (click → signup)
- Verifies the lead API endpoint is reachable
test sale
- Sends a test sale event with a mock transaction
- Confirms revenue attribution works (customer → affiliate)
- Verifies amount and currency handling
Check Overall Status
npx affitor status
Shows:
- Program configuration
- Stripe connection status (if using Stripe auto-setup)
- Recent event counts (last 24 hours)
Troubleshooting
| Issue | Fix |
|---|---|
| "No config found" | Run npx affitor init first |
| "Invalid API key" | Re-run npx affitor init to get a new key |
| "Click test passed but lead failed" | Check that customer_key matches between signup and sale calls |
| "Sale test shows $0 commission" | Verify commission rate is set in your program settings |
Debug Mode
For browser-side tracking issues, enable debug mode to see events in the browser console:
<script src="https://api.affitor.com/js/affitor-tracker.js"
data-affitor-program-id="YOUR_PROGRAM_ID"
data-affitor-debug="true">
</script>
Or with the SDK:
const affitor = await loadAffitor('YOUR_PROGRAM_ID', { debug: true });
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 First seen · 83 lines · 33 tokens per session scan A 24eb19210a89
test-integration is a skill published in the GitHub repository Affitor/agent-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 505 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
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…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work. Render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.