CCFA Skills is a family of agent skills that helps researchers develop the storyline and presentation of CCF-A research papers. It supports work across research ideas, literature, experiments, writing, figures, reviews, rebuttals, and submission while keeping the argument connected. The catalogue entry consists of the project's research-writing skills and plugin.
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 mikubaka88/CCFA-Skills --skill ccf-pipeline-orchestratorgit clone --depth 1 https://github.com/mikubaka88/CCFA-SkillsWrote 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/mikubaka88/ccfa-skills/ccf-pipeline-orchestrator)<a href="https://agentmods.dev/skills/mikubaka88/ccfa-skills/ccf-pipeline-orchestrator"><img src="https://agentmods.dev/badge/skills/mikubaka88/ccfa-skills/ccf-pipeline-orchestrator/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/mikubaka88/ccfa-skills/ccf-pipeline-orchestrator"><img src="https://agentmods.dev/badge/skills/mikubaka88/ccfa-skills/ccf-pipeline-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00068 | $0.00806 |
| Opus 5 | $0.00034 | $0.00403 |
| Sonnet 5 | $0.00014 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
ccf-pipeline-orchestrator 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 6d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCF Pipeline Orchestrator
Core Rule
Operate as the project coordinator and workflow planner. Clarify the goal, map the current stage, update or read ccfa.yaml, define gates, and name the next owner skill. Specialist skills own downstream outputs. For a plan-only request, return the plan. For explicitly requested end-to-end execution, coordinate the authorized owners through completion rather than stopping after naming the next skill. Follow ../ccf-common/references/task-modes.md: if the user asks for a short plan, checklist, YAML update, table, or narrative roadmap, use that visible shape instead of forcing a fixed report.
Place ccf-humanization before any handoff that will write manuscript text or create publication-facing experiment artifacts. This priority preflight does not replace the downstream owner and requires no extra handoff question.
Follow ../ccf-common/references/handoff-modes.md and ../ccf-common/references/artifact-contracts.md. Later user corrections normally steer the active project: preserve valid completed work, update affected requirements, and continue. Do not invent completed stages or automatic background jobs.
Workflow
- Identify target venue, current stage, available artifacts, constraints, deadline pressure, and the user's immediate goal.
- Read
ccfa.yamlwhen available; if absent, continue with supplied artifacts and report that project-state tracking is unavailable. - For unclear projects, use
references/workflow-planning/intake-protocol.md,approach-options.md, anddesign-brief-template.md. - Classify the next owner:
ccf-project-scaffolder,ccf-idea-optimizer,ccf-idea-reviewer,ccf-literature-monitor,ccf-literature-searcher,ccf-experiment-designer,ccf-visual-composer,ccf-paper-to-exemplar,ccf-paper-writer,ccf-paper-reviewer,ccf-integrity-auditor,ccf-submission-checker, orccf-rebuttal-writer. Prefixccf-humanizationwhen the output will enter a manuscript or publication-facing experiment artifact. - Define the gate: required input, output artifact, pass condition, blocker, and handoff.
- Resolve canonical input/output and working paths before each file-producing handoff. Reuse the current artifact and hand off changed requirements plus source locations, not duplicated full reports. Keep independent owners from writing the same file concurrently. Update existing
ccfa.yamlstage/gate fields when project-state maintenance is authorized; preserve unrelated fields and the existing contract. For a planning-only request, propose the update without writing. Reuse existing artifact/state fields for the current goal, evidence locations, completed work, and next step when continuation needs it.
What ships with it
4 files 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.
- 6d ago Changed · +2 lines · -36 tokens per session 65995c6d29c4
- 13d ago First seen · 45 lines · 104 tokens per session scan A 6bde3d595a2c
ccf-pipeline-orchestrator is a skill published in the GitHub repository mikubaka88/CCFA-Skills (2,422 stars, last pushed 6d ago), licensed MIT. It adds 68 tokens to every session and 806 once invoked, about $0.0003 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…