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 frankxai/claude-skills-library --skill creator-productivitygit clone --depth 1 https://github.com/frankxai/claude-skills-libraryWrote 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/frankxai/claude-skills-library/creator-productivity)<a href="https://agentmods.dev/skills/frankxai/claude-skills-library/creator-productivity"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/creator-productivity/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/frankxai/claude-skills-library/creator-productivity"><img src="https://agentmods.dev/badge/skills/frankxai/claude-skills-library/creator-productivity.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.00062 | $0.00759 |
| Opus 5.5 | $0.00025 | $0.00304 |
| Sonnet 5.5 | $0.00012 | $0.00152 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
creator-productivity 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creator Productivity
Structured task management and memory for creative work — projects don't slip, context doesn't reset.
Architecture
TASKS.md ← Task board (Active, In Progress, Done)
CREATOR.md ← Working memory (voice, projects, quick-ref)
creator-memory/
voice.md ← Full brand voice documentation
visual.md ← Visual style system
music.md ← Music style and track log
channels.md ← Per-channel content rules
projects/ ← Active project briefs
content/ ← Content catalog (published + drafts)
This two-tier system keeps the hot cache lean (CREATOR.md at ~80 lines) while supporting unlimited depth in creator-memory/.
Task Management
TASKS.md Format
# Tasks
## Active
- [ ] **[Task title]** — [context, relevant project, deadline if any]
- [Additional detail if needed]
## In Progress
- [ ] **[Task title]** — [started date, blocker if any]
## Done (last 2 weeks)
- [x] ~~[Completed task]~~ ([completion date])
Rules:
- Bold the title for scannability
- Include enough context to work without re-explaining
- Move to Done immediately on completion, not "later"
- Archive Done section weekly (move to
creator-memory/content/archive.md)
Task capture from conversation
When the user mentions something that should be tracked ("I need to write the Suno launch post", "follow up with the design team"), extract and add it automatically:
- Infer title and context from conversation
- Add to Active with today's date
- Confirm: "Added to TASKS.md: [title]. Is that right?"
Creator Memory System
Two-tier lookup for every creative request:
User request →
1. Check CREATOR.md (hot cache — covers 90% of daily needs)
2. If not found → creator-memory/ (deep files)
3. If still not found → ask user, then save
Lookup examples:
- "write a linkedin post" → load voice attributes + LinkedIn channel rules from CREATOR.md
- "create a blog hero image" → load visual style from CREATOR.md, fall back to creator-memory/visual.md
- "finish the [project] brief" → load project brief from creator-memory/projects/[project].md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 95 lines · 62 tokens per session scan A c389ccfd5ae1
creator-productivity is a skill published in the GitHub repository frankxai/claude-skills-library (47 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 759 once invoked, about $0.0002 per session on Opus 5.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
wayfinder
A planning method that maps a large, uncertain project into linked decision tickets in a repository's issue tracker. An issue tracker is a system for recording and organizing project work.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
to-tickets
A method for turning a plan, specification, or conversation into small tickets, where each ticket is a complete vertical slice of work and lists the tickets that must come first.
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
session-memory-manager
Manages the entire session lifecycle: from context loading (PRD, Tech Stack) at startup, to maintaining project memory during active sessions, and creating ultra-compact checkpoints for handoff. / Mengelola siklus hidup sesi: dari pemuatan konteks awal, pemeliharaan memori proyek, hingga pembuatan checkpoint ringkas…