signup-tracking

signup-tracking is a skill for Claude Code, Codex from Affitor/agent-skills. It costs 36 tokens per session (507 once invoked), scanned B, original, MIT.

An affiliate-signup tracking tool that records when a user registers after arriving through a partner link. Affiliate attribution connects that registration to the partner who referred the user.

In plain words
What is it for?
Recording successful registrations with the Affitor tracking service, using a browser helper, npm package, or server-side lead request.
Why use it?
It removes the need to match signups to referral clicks by hand. The tracking can be sent from the browser or from your server.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Recording successful registrations with the Affitor tracking service, using a browser helper, npm package, or server-side lead request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/affitor/agent-skills/signup-tracking
Install

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.

Any agent
npx skills add Affitor/agent-skills --skill signup-tracking
Clone the repo
git clone --depth 1 https://github.com/Affitor/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for signup-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/affitor/agent-skills/signup-tracking.svg)](https://agentmods.dev/skills/affitor/agent-skills/signup-tracking)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 507 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.00507
Opus 5 $0.00018 $0.00253
Sonnet 5 $0.00007 $0.00101
Haiku 4.5 $0.00004 $0.00051

Measured 8d ago against content hash 0db7daee2f66, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 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.

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(
skills/tracking/signup-tracking/SKILL.md · 89 lines

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_id or customer_key
  • The customer_key must 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
Changes

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.

  1. 8d ago First seen · 89 lines · 36 tokens per session scan B 0db7daee2f66

Subscribe to this mod's changes

signup-tracking is a skill published in the GitHub repository Affitor/agent-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 507 once invoked, about $0.0002 per session on Opus 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens