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/reggiechan74/jobops/copywritenpx skills add reggiechan74/JobOps --skill copywritegit clone --depth 1 https://github.com/reggiechan74/JobOpsWrote 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/reggiechan74/jobops/copywrite)<a href="https://agentmods.dev/skills/reggiechan74/jobops/copywrite"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/copywrite.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.02222 |
| Opus 5 | $0.00008 | $0.01111 |
| Sonnet 5 | $0.00003 | $0.00444 |
| Haiku 4.5 | $0.00002 | $0.00222 |
Grade A, and why
copywrite 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 3d 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration
Read .jobops/config.json. If missing, stop with:
JOBOPS NOT CONFIGURED Run /jobops:setup (then /jobops-ic:setup) to initialize your workspace.
Use config.directories.contractor_root for output paths in this skill.
Use config.preferences.default_currency for pricing if applicable.
Arguments
I'll generate strategic landing page copy using proven copywriting frameworks and persuasion psychology.
$1: Page purpose/topic (required) - e.g.,consulting-services,saas-product,event-registration--tone: Writing tone (optional):professional|casual|bold(default: professional)--framework: Copywriting framework (optional):PAS|AIDA|StoryBrand(default: PAS)
Copywriting Frameworks
PAS (Problem-Agitate-Solution) - Default
Best for: Services, consulting, B2B offerings
| Stage | Purpose | Landing Page Section |
|---|---|---|
| Problem | Identify the pain | Hero subtitle, Problem section |
| Agitate | Intensify the urgency | Statistics, consequences |
| Solution | Present your offering | Benefits, How It Works |
AIDA (Attention-Interest-Desire-Action)
Best for: Products, e-commerce, direct response
| Stage | Purpose | Landing Page Section |
|---|---|---|
| Attention | Hook with headline | Hero title |
| Interest | Build curiosity | Problem/opportunity |
| Desire | Create want | Benefits, social proof |
| Action | Drive conversion | CTA sections |
StoryBrand
Best for: Brand building, services, complex offerings
| Element | Purpose | Landing Page Section |
|---|---|---|
| Hero (Customer) | Position visitor as hero | Hero messaging |
| Problem | Define villain/challenge | Problem section |
| Guide (You) | Position as trusted guide | Credentials, about |
| Plan | Show clear path | How It Works |
| Call to Action | Direct next step | CTA sections |
| Success/Failure | Paint outcomes | Benefits/consequences |
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.
- 3d ago First seen · 296 lines · 16 tokens per session scan A 240f6b511429
copywrite is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 2,222 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.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…