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 oyusypenko/creo --skill creo-contentgit clone --depth 1 https://github.com/oyusypenko/creoWrote 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/oyusypenko/creo/creo-content)<a href="https://agentmods.dev/skills/oyusypenko/creo/creo-content"><img src="https://agentmods.dev/badge/skills/oyusypenko/creo/creo-content/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/oyusypenko/creo/creo-content"><img src="https://agentmods.dev/badge/skills/oyusypenko/creo/creo-content.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.00073 | $0.01286 |
| Opus 5 | $0.00036 | $0.00643 |
| Sonnet 5 | $0.00015 | $0.00257 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
creo-content 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 12d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing Content Strategy
Create compelling, conversion-focused marketing copy based on customer pain points, JTBD framework, and competitive advantages. Output is i18n-ready JSON for integration with internationalization systems.
Commands
| Command | Description |
|---|---|
/creo content landing |
Generate landing page content |
/creo content feature |
Generate feature page content |
/creo content pricing |
Generate pricing page content |
/creo content <page-type> |
Generate content for any page type |
Core Instructions
Configuration
- Check for project-specific config at
.claude/project-config.md - Read
project_id,project_name,project_url,locales,voice_and_tone,content_path - Load project extension if it exists at
.claude/skills/creo-content/creo-content-{project_id}.md. This file contains project-specific brand voice, tone, target audience, JTBD, pain points, and i18n conventions.{project_id}comes fromproject-config.md. Always load it before doing work. - If no config exists, use defaults or ask user
Pain Point Psychology
Customers buy solutions to problems. Identify:
- Functional pains: Time wasted, manual work, errors
- Emotional pains: Frustration, anxiety, embarrassment
- Financial pains: High costs, hidden fees, unpredictable pricing
- Social pains: Looking incompetent, missing deadlines
JTBD Framework
Every piece of content connects to a specific customer job:
When [SITUATION/CONTEXT],
I want to [MOTIVATION/ACTION],
So I can [EXPECTED OUTCOME/BENEFIT].
Content Creation Process
Step 1: Understand the Context
- Read the target page/section requirements
- Identify the primary audience segment
- Review pain points for that segment
- Check competitive messaging opportunities
Step 2: Apply JTBD Framework
- Who is the customer? (segment)
- What job are they trying to do?
- What pain points block them?
- How does the product solve this?
- What outcome do they achieve?
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.
- 12d ago First seen · 184 lines · 73 tokens per session scan A 723068c0c2c4
creo-content is a skill published in the GitHub repository oyusypenko/creo (4 stars, last pushed 3d ago), licensed MIT. It adds 73 tokens to every session and 1,286 once invoked, about $0.0004 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
agent-loop-ext
Crash-resilient external agent loop with state persistence and CI/CD integration.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
ci-status
Show current pipeline status for the active branch (GitLab CI or GitHub Actions).
devops
DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.