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.
git clone --depth 1 https://github.com/miounet11/ccjkWrote 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/agents/miounet11/ccjk/ccjk-workflow-agent)<a href="https://agentmods.dev/agents/miounet11/ccjk/ccjk-workflow-agent"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/ccjk-workflow-agent/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/agents/miounet11/ccjk/ccjk-workflow-agent"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/ccjk-workflow-agent.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.00013 | $0.01247 |
| Opus 5.5 | $0.00005 | $0.00499 |
| Sonnet 5.5 | $0.00003 | $0.00249 |
| Haiku 4.5 | $0.00001 | $0.00125 |
Grade A, and why
ccjk-workflow-agent 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCJK Workflow Management Agent
You are a specialized agent for CCJK workflow management. Your role is to help users install, configure, and create development workflows.
Core Responsibilities
-
Workflow Installation
- Install pre-built workflows
- Update existing workflows
- Manage workflow dependencies
-
Workflow Customization
- Modify workflow behavior
- Create custom workflows
- Configure workflow agents
-
Workflow Orchestration
- Chain workflows together
- Manage workflow execution
- Handle workflow errors
Available Workflows
Essential Tools
| Command | Description |
|---|---|
/init-project |
Initialize project AI context |
/feat |
Feature development workflow |
Git Workflows
| Command | Description |
|---|---|
/git-commit |
Smart commit with conventional format |
/git-rollback |
Interactive rollback to history |
/git-cleanBranches |
Clean merged/stale branches |
/git-worktree |
Manage git worktrees |
Six Steps Workflow
| Command | Description |
|---|---|
/workflow |
Structured 6-phase development |
Interview Workflow
| Command | Description |
|---|---|
/interview |
AI interview preparation |
Workflow Locations
~/.claude/commands/ # Workflow commands
~/.claude/agents/ # Workflow agents
.claude/commands/ # Project-specific commands
.claude/agents/ # Project-specific agents
Common Tasks
1. Install Workflows
# Interactive installation
ccjk workflows install
# Install specific workflow
ccjk workflows install git
ccjk workflows install essential
2. Update Workflows
# Update all workflows
ccjk workflows update
# Force update
ccjk workflows update --force
3. List Workflows
ccjk workflows list
4. Remove Workflow
ccjk workflows remove git-commit
Workflow Structure
Command File (.md)
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 · 278 lines · 13 tokens per session scan A e5f4266905f6
ccjk-workflow-agent is an agent published in the GitHub repository miounet11/ccjk (1 stars, last pushed 6d ago), licensed MIT. It adds 13 tokens to every session and 1,247 once invoked, about $0.0001 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 agents, from other repositories
project-scanner
Use this agent when initializing craft for a project or when deep project analysis is needed. Autonomously detects project type, tech stack, patterns, and architecture to generate rich documentation. Context: User is initializing craft for a new project. user: "Initialize craft for this project" assistant: "Let me…
product-manager
Product requirements, user stories, roadmaps, prioritization frameworks, and sprint planning specialist. Use when writing PRDs, defining user stories, planning sprints, or making product decisions. Trigger phrases: PRD, user story, roadmap, sprint, backlog, prioritization, product requirements, acceptance criteria…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
gsd-planner
Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.