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/payrequest/copana/customizenpx skills add PayRequest/copana --skill customizegit clone --depth 1 https://github.com/PayRequest/copanaWhat 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.00000 | $0.00423 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
customize 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.
What it actually says
/customize — Guided Customization
Help the user customize their Copana setup by modifying the codebase directly.
When to use
Run when the user wants to change how their AI works, add new features, or adjust behavior.
How it works
-
Ask what they want to change. Common options:
- Change the AI's personality or vibe
- Add new memory files (e.g., fitness.md, budget.md)
- Modify the startup ritual
- Add new accountability areas
- Change notification preferences
- Add new automation scripts
-
Read the relevant files to understand current state.
-
Make the changes directly — edit the markdown files or scripts. Copana is designed to be modified.
-
Update CLAUDE.md if you added new files — add them to the file registry table.
-
Commit the changes with a descriptive message.
Common customizations
Add a new domain file
- Create the
.mdfile with section headers - Add it to CLAUDE.md file registry table
- Reference it in the relevant section of CLAUDE.md
Change personality
- Edit
soul.mdfor values and identity - Edit
personality.mdfor communication style - The AI will follow the updated personality next session
Add accountability
- Add the area to
personality.mdaccountability section - Add relevant checks to
proactive_ping.pyif automation is wanted
Add a new automation
- Create script in
scripts/following the pattern of existing scripts - Use
copana_utils.pyfor notifications, AI calls, logging - Add to
crontab.example - Add to
scripts/README.md
Principles
- Keep it simple — don't over-engineer
- Modify code directly, don't add config layers
- If adding a file, update CLAUDE.md registry
- Commit changes so they're version-controlled
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 · 54 lines · 0 tokens per session scan A bb4b016ceb33
customize is a skill published in the GitHub repository PayRequest/copana (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 423 tokens. 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
npm-package
Opinionated TypeScript npm package template for ESM packages. Enforces src→dist builds with tsc, strict TypeScript defaults, explicit exports, and publish-safe package metadata. Relative source imports must use .ts or .tsx (never .js); tsc rewrites them via rewriteRelativeImportExtensions. Use this when creating or…
new-skill
Best practices for creating a SKILL.md file. Covers file structure, frontmatter, writing style, and where to place skills in a repository. Use when the user wants to create a new skill, update an existing skill, write a SKILL.md, or asks how skills work.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
find-skills
Run this BEFORE any package install (pip / npm / apt / brew / cargo / gem / go install) you would otherwise execute via the exec tool — including when the user asks for a deliverable that needs third-party libraries (PDF generation, image processing, scrapers, dashboards, charts, OCR, audio/video, …). It searches the…
fastclaw-skill-guide
Create new skills for FastClaw agents. Use when the user asks to create a skill, turn a workflow into a skill, or build reusable automation. Also use when discussing skill format, structure, or best practices.
fastclaw-api-integration
Use this skill when integrating an upstream application with FastClaw as an agent runtime.