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/commands/miounet11/ccjk/feat)<a href="https://agentmods.dev/commands/miounet11/ccjk/feat"><img src="https://agentmods.dev/badge/commands/miounet11/ccjk/feat/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/commands/miounet11/ccjk/feat"><img src="https://agentmods.dev/badge/commands/miounet11/ccjk/feat.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.00003 | $0.00599 |
| Opus 5.5 | $0.00001 | $0.00240 |
| Sonnet 5.5 | $0.00001 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
feat 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 2mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ARGUMENTS
Core Workflow
1. Input Analysis and Type Determination
When receiving user input, first perform type determination and clearly inform the user:
Determination Criteria:
-
Requirement Planning Type: User proposes new feature requirements, project ideas, or needs to formulate plans
-
Discussion Iteration Type: User requests to continue discussion, modify, or refine existing planning
-
Execution Implementation Type: User confirms planning is complete and requests to start specific implementation work
2. Classification Processing Mechanism
A. Requirement Planning Processing
Trigger Condition: Identified as functional requirement input
Execution Actions:
-
Enable Planner Agent
-
Generate detailed markdown planning document
-
Store document in
./.claude/plandirectory, named in plan/xxx.md format -
Include: objective definition, feature breakdown, implementation steps, acceptance criteria
B. Discussion Iteration Processing
Trigger Condition: User requests to continue discussion or modify planning
Execution Actions:
-
Retrieve and analyze previously generated planning files
-
Identify user feedback and confirmation content
-
Enable Planner Agent
-
Generate detailed markdown planning document
-
Create a new document, for example, if the last one was plan/xxx.md, then this time it's plan/xxx-1.md, if the last one was plan/xxx-1.md, then this time it's plan/xxx-2.md, and so on
-
Reorganize pending implementation task priorities
C. Execution Implementation Processing
Trigger Condition: User confirms planning is complete and requests to start execution
Execution Actions:
-
Start task execution in the order of planning documents
-
Perform task type identification before each subtask begins
-
Frontend Task Special Processing:
-
Check if available UI design exists
-
If no design solution exists, must use UI-UX-Designer Agent
-
Complete UI design before proceeding with development implementation
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.
- 2mo ago First seen · 106 lines · 3 tokens per session scan A 9c8b2342827e
feat is a command published in the GitHub repository miounet11/ccjk (1 stars, last pushed 7d ago), licensed MIT. It adds 3 tokens to every session and 599 once invoked, about $0.0000 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 commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
discuss
A command that interviews you in five phases and saves a detailed description of a proposed feature or change. EARS is a structured way to write requirements so they can be checked clearly.
adr
A command that records important, difficult-to-reverse technical choices as Architecture Decision Records, or ADRs.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.