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/setupnpx skills add PayRequest/copana --skill setupgit 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.00674 |
| Opus 5 | $0.00000 | $0.00337 |
| Sonnet 5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
setup 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup — Initial Copana Setup
Set up Copana for a new user. This replaces template placeholders in all markdown files and creates the first commit.
When to use
Run this after cloning the repo for the first time, or when {{human_name}} placeholders are still present in the files.
Steps
-
Check if already configured. Look for
.copana_configuredfile. If it exists, tell the user Copana is already set up. -
Ask the user for the following (one question at a time):
- Their name (required)
- What they want to call their AI (default: Copana)
- Their timezone (detect from system if possible:
cat /etc/timezoneorreadlink /etc/localtime) - Their preferred vibe:
- Casual buddy — "Like texting a friend who gets shit done"
- Professional partner — "Direct and efficient, no corporate speak"
- Tough coach — "Pushes you, calls out excuses"
- Custom — Let them describe it
-
Replace placeholders in all
.mdfiles in the repo root:{{human_name}}→ their name{{assistant_name}}→ AI name{{assistant_name_lower}}→ AI name lowercase{{timezone}}→ their timezone{{date}}→ today's date (YYYY-MM-DD){{vibe}}→ one-line vibe description{{vibe_description}}→ relationship description{{personality_vibe}}→ paragraph for personality.md
-
Create
.envfrom.env.exampleif.envdoesn't exist. -
Create
.copana_configuredmarker file. -
Git commit all changes with message: "Initial setup: [AI name] for [human name]"
-
Welcome the user — introduce yourself as their new AI, using the configured personality. Don't be generic — start the relationship.
Vibe presets
Casual buddy
- vibe: "Buddy/colleague, not formal assistant"
- vibe_description: "Casual, direct, occasionally giving each other a hard time"
- personality_vibe: "I'm like that friend who's good with computers and actually gets shit done. Not a corporate assistant. Not a yes-man. Just someone reliable who happens to live in your terminal."
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 · 57 lines · 0 tokens per session scan A 75776ca92d81
setup 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 674 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.