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 technicalpickles/pickled-claude-plugins --skill come-ongit clone --depth 1 https://github.com/technicalpickles/pickled-claude-pluginsWrote 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/technicalpickles/pickled-claude-plugins/come-on)<a href="https://agentmods.dev/skills/technicalpickles/pickled-claude-plugins/come-on"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/come-on/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/technicalpickles/pickled-claude-plugins/come-on"><img src="https://agentmods.dev/badge/skills/technicalpickles/pickled-claude-plugins/come-on.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.00219 | $0.00958 |
| Opus 5.5 | $0.00088 | $0.00383 |
| Sonnet 5.5 | $0.00044 | $0.00192 |
| Haiku 4.5 | $0.00022 | $0.00096 |
Grade A, and why
come-on 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 23d 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
come on
Don't stop short. Do the cheap work, then make it land.
Mode
Arguments: "$ARGUMENTS"
- Empty: you're here on your own or the user said "come on". Pick the angles that fit the turn you're about to send (or the one the user is reacting to).
- Starts with a mode (
check,try,rederive,weigh,unpack,simplify): run that angle on the last reply, plus any other that obviously applies. The rest of the arguments name the target: a claim, a reader (unpack for my skip-level), or a shape (simplify for slack).
The core (every angle)
- List the loose claims. Go through the reply you're about to send (or just sent) and pull out every statement the user will act on that you haven't verified this turn: a claim of done or fixed, a "can't", something inherited from a handoff or old conclusion, an option set you haven't weighed. Usually there are several. Each gets its own check.
- Do the cheap work for each one, for each angle that fired. Independent checks run in parallel.
- Reply in this shape:
- The answer first, in plain words. If a check flipped something you said earlier, that comes first.
- Then one line per claim: what you checked, what you found.
- Then anything you couldn't check, and why.
Why: the user can't see what you didn't check. A claim built on memory reads exactly like one built on evidence, and they pay for it later.
Skip when the step is trivial and easy to undo, or the claim rests on output from this same turn. If you're arguing with yourself about whether it's trivial, it isn't.
Angles
| Angle | Before you… | The cheap work |
|---|---|---|
| check | claim done / fixed / found / pre-existing | verify it this session; reproduce "pre-existing" on a clean base |
| try | say can't / blocked / "say the word" | retry transients once, try the next tool, just do read-only things |
| rederive | build on a handoff or old conclusion | say where it came from and how old, re-check against current evidence |
| weigh | put options in front of the user | drop fake options, find prior art, tradeoffs with evidence, recommend |
| unpack | ask a question or offer options | define every ID and label for a reader who wasn't there |
| simplify | send a long reply | answer first, a few bullets, stop |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago Changed · +1 lines 02fe1f62ede3
- 28d ago Changed · -29 lines · -64 tokens per session 709d660b0c29
- 1mo ago First seen · 82 lines · 283 tokens per session scan A 324ca5579101
come-on is a skill published in the GitHub repository technicalpickles/pickled-claude-plugins (12 stars, last pushed today), licensed MIT. It adds 219 tokens to every session and 958 once invoked, about $0.0009 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-10-09.
come-on compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| come-ontechnicalpickles/pickled-claude-plugins | Skill | 12 | today | MIT | A | 219 | Claude Code |
| create-agent-dotnetdiagrid-labs/dapr-skills | Skill | 13 | 4d ago | MIT | A | 58 | Claude Code |
| create-pubsub-dotnetdiagrid-labs/dapr-skills | Skill | 13 | 4d ago | MIT | A | 79 | Claude Code |
| create-pubsub-pythondiagrid-labs/dapr-skills | Skill | 13 | 4d ago | MIT | A | 70 | Claude Code |
| create-workflow-from-diagramdiagrid-labs/dapr-skills | Skill | 13 | 4d ago | MIT | A | 97 | Claude Code |
| create-workflow-typescriptdiagrid-labs/dapr-skills | Skill | 13 | 4d ago | MIT | A | 69 | Claude Code |
| create-workflow-dotnetdiagrid-labs/dapr-skills | Skill | 13 | 4d ago | MIT | A | 52 | Claude Code |