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 signup-trackinggit 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/signup-tracking)<a href="https://agentmods.dev/skills/affitor/agent-skills/signup-tracking"><img src="https://agentmods.dev/badge/skills/affitor/agent-skills/signup-tracking/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/signup-tracking"><img src="https://agentmods.dev/badge/skills/affitor/agent-skills/signup-tracking.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.00036 | $0.00507 |
| Opus 5.5 | $0.00014 | $0.00203 |
| Sonnet 5.5 | $0.00007 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade B, and why
signup-tracking scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
requests.post( 'https://api.affitor.com/api/v1/track/lead', Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
requests.post( What it actually says
Signup Tracking
After a user registers, notify Affitor so the signup is linked to the referring affiliate partner.
Browser-Side (requires tracker script)
// Call after signup succeeds
await window.affitor.signup(user.id, user.email);
With the npm SDK:
import { loadAffitor } from '@affitor/tracker';
const affitor = await loadAffitor('YOUR_PROGRAM_ID');
await affitor?.signup(user.id, user.email);
Server-Side (Lead API)
POST https://api.affitor.com/api/v1/track/lead
Authorization: Bearer YOUR_PROGRAM_API_KEY
Content-Type: application/json
{
"customer_key": "user_123",
"email": "[email protected]",
"click_id": "from_affitor_click_id_cookie"
}
Node.js
await fetch('https://api.affitor.com/api/v1/track/lead', {
method: 'POST',
headers: {
'Authorization': `Bearer ${process.env.AFFITOR_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({
customer_key: newUser.id,
email: newUser.email,
click_id: req.cookies.affitor_click_id,
}),
});
Python
requests.post(
'https://api.affitor.com/api/v1/track/lead',
headers={
'Authorization': f'Bearer {AFFITOR_API_KEY}',
'Content-Type': 'application/json',
},
json={
'customer_key': str(new_user.id),
'email': new_user.email,
'click_id': request.cookies.get('affitor_click_id'),
},
)
Rules
- Provide at least one of
click_idorcustomer_key - The
customer_keymust be your internal user ID, reused later in sale tracking - Browser-side
signup()is simplest when the tracker is already on the page
Test
npx affitor test lead
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 · 89 lines · 36 tokens per session scan B 0db7daee2f66
signup-tracking is a skill published in the GitHub repository Affitor/agent-skills (3 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 507 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…