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 agentmods add skills/merencia/pairwith/create-profilenpx skills add merencia/pairwith --skill create-profilegit clone --depth 1 https://github.com/merencia/pairwithWhat 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 | $0.00041 | $0.02081 |
| Opus 5 | $0.00020 | $0.01040 |
| Sonnet 5 | $0.00008 | $0.00416 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
create-profile 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.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
create-profile
Generate a profiles/<handle>.md style profile ready to submit to pairwith, following the project's policy.
What this skill generates (and what it does not)
This skill creates a community AI style profile — a set of prompt instructions inspired by publicly observable aspects of a developer's technical work. A profile is not the real person, does not represent them, and is not endorsed by or affiliated with them unless explicitly stated and documented.
Before generating anything, read or re-read:
TEMPLATE.md— the required structure and mandatory non-impersonation header.PROFILE_POLICY.md— eligibility, consent tiers, naming, content, and safety rules.DISCLAIMER.md— the overall project posture.
If you cannot read these files (e.g. running outside the repo), apply the principles summarized below from memory.
Invocation
/create-profile [github-handle] [urls...] [file-path]
Examples:
/create-profile
/create-profile caarlos0
/create-profile caarlos0 carlosbecker.com linkedin.com/in/caarlos0
/create-profile merencia merencia.com ./notes-about-my-style.md
/create-profile caarlos0 https://github.com/caarlos0/dotfiles/blob/main/skills/pair-with-caarlos0/SKILL.md
Step 1 — gather inputs
Parse the invocation arguments:
- GitHub handle: the first word if it doesn't start with
http,/, or.. If not provided, ask: "What's the GitHub handle for this profile?" - URLs: any argument starting with
httpor a bare domain. Only accept URLs that are clearly public (personal sites, blogs, LinkedIn public pages, public talks, public articles, public repositories). - File path: any argument starting with
/,./, or ending in.mdor.txt. Read the file contents. Only use content that is plainly public or provided by the user about themselves.
If no URLs and no file are provided after getting the handle, ask: "Any useful public links or a reference file? (personal site, public LinkedIn, blog, public talks, existing public style guide, etc.) — or just press enter to generate from public GitHub alone."
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.
- 2d ago First seen · 155 lines · 41 tokens per session scan A efa36f72051f
create-profile is a skill published in the GitHub repository merencia/pairwith (7 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 2,081 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.