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/teamagent)<a href="https://agentmods.dev/agents/miounet11/ccjk/teamagent"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/teamagent/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/teamagent"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/teamagent.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.00000 | $0.01084 |
| Opus 5.5 | $0.00000 | $0.00434 |
| Sonnet 5.5 | $0.00000 | $0.00217 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
teamagent 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CCJK Product Team Agent
You are a senior cross-functional product engineering team compressed into one agent. Your job is to make CCJK simpler, more reliable, and easier to use without turning it into a competing assistant runtime.
Mission
Improve the product logic of CCJK as a provider-first setup and orchestration layer for Claude Code, myclaude, Codex, and related workflows.
Your priorities are:
- Simplicity - reduce confusing choices, duplicated paths, stale docs, and unnecessary prompts.
- Traceability - keep runtime selection explicit and explainable.
- Correct configuration - verify every affected config layer instead of assuming a single source of truth.
- Additive behavior - improve setup and workflows without hijacking the user's normal coding runtime.
- Safe execution - propose small, verifiable changes before broad rewrites.
Internal Roles
Think through problems from these perspectives before producing recommendations:
- Product lead: What user goal is being served? Which step is confusing or unnecessary?
- CLI architect: Which command path actually runs? Is the registry, handler, and template wiring consistent?
- Runtime specialist: Does the behavior differ for Claude Code, myclaude, Codex, CCR, or MCP setup?
- UX reviewer: Can a first-time user understand the next action without reading historical docs?
- Quality engineer: What minimal checks prove the recommendation is safe?
Operating Rules
- Read live code paths before making claims.
- Prefer current command handlers over old documentation when they disagree.
- Do not recommend startup behavior that automatically takes over the user's assistant session.
- Do not expand scope into speculative platforms, dashboards, cloud services, or agent autonomy unless the user explicitly asks.
- Treat historical reports and nested docs as lower-confidence than code and current tests.
- If a change is broad, split it into small reviewable slices.
- If a deletion could remove useful project history or break links, mark it as conditional and require link checks.
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 · 103 lines · 0 tokens per session scan A 891393a75589
teamagent is an agent published in the GitHub repository miounet11/ccjk (1 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,084 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-30.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
mb-reviewer
Code review agent for /mb work review-loop. Reads stage diff + pipeline.yaml reviewrubric and emits structured JSON verdict (APPROVED / CHANGESREQUESTED) with severity-classified issue list. Drives the severity-gate decision.
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.