capture

A local list of websites and search terms whose rankings you want to track. It uses DataForSEO's search-result data to check their positions again and compare them with the previous check.

In plain words
What is it for?
Use it to monitor your own or competitors' domains, target keywords, ranking gains, losses, and drops.
Why use it?
It makes ranking changes visible over time instead of requiring repeated manual searches and note-taking.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/perpetualsoftware/pad/capture
Any agent
npx skills add PerpetualSoftware/pad --skill capture
Clone the repo
git clone --depth 1 https://github.com/PerpetualSoftware/pad

Made for: Claude Code, Codex.

Per session 10 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 517 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00010 $0.00517
Opus 5 $0.00005 $0.00259
Sonnet 5 $0.00002 $0.00103
Haiku 4.5 $0.00001 $0.00052

Measured 2d ago against content hash 19c3e2c67b75, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

capture 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 2d 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.

plugin/skills/capture/SKILL.md · 40 lines

What it actually says

If the pad CLI is missing (command not found), say so and point at https://getpad.dev/install — don't retry or guess at alternate paths. If no .pad.toml is found in the directory tree, first run pad auth whoami (fast, safe, never blocks): if it shows a real user, this machine is already set up — run pad workspace init to link and create the workspace non-interactively, then continue capturing. If it reports anything else (not configured, session expired), this machine hasn't finished setup — don't run pad init/pad workspace init yourself. Both now fail fast when stdin/stdout aren't terminals instead of hanging (BUG-2538/BUG-2577/ BUG-2592) — though on a harness whose stdin AND stdout look like a real terminal they still drop into the browser flow — and either way the outcome just means a human needs an interactive terminal, which doesn't help you. Tell the user to run pad init themselves in an interactive terminal (in Claude Code, suggest ! pad init) and stop.

Before creating, run pad item list conventions --field trigger=always --field status=active --format json --full and apply whatever it returns — always-on conventions are project rules the workspace has made mandatory (privacy, sizing, format, etc.), and low-ceremony capture means skipping the full bootstrap weight (dashboard, playbooks, roles), not skipping mandatory rules. This is the only context load this skill does; it's deliberately narrower than the main skill's full bootstrap.

Capture $ARGUMENTS into the Pad workspace as the item type it most resembles (idea, task, bug, note), following any conventions just loaded. Run pad collection list --format json to see the workspace's collections, pick the best fit, then show what you're about to create (collection, title, content) and confirm before running pad item create <collection> "<title>" --content "...". Keep the title short; put nuance in the content.

Exception: if any loaded convention explicitly opts into autonomous capture, skip the confirmation — create immediately and confirm with the new issue ID in one line, no ceremony. Confirm-first is the default for everyone else.

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. 2d ago First seen · 40 lines · 10 tokens per session scan A 19c3e2c67b75

Subscribe to this mod's changes

capture is a skill published in the GitHub repository PerpetualSoftware/pad (146 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 517 once invoked, about $0.0001 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.