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 agentmods add commands/jonase47/ccpr/konzept-updategit clone --depth 1 https://github.com/jonase47/ccprWrote 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/jonase47/ccpr/konzept-update)<a href="https://agentmods.dev/commands/jonase47/ccpr/konzept-update"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/konzept-update.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01398 |
| Opus 5 | $0.00000 | $0.00699 |
| Sonnet 5 | $0.00000 | $0.00280 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
konzept-update 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 today.
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/konzept-update – Revise an existing rough concept
Purpose
This command updates an existing rough concept based on new findings, clarified open questions, or changed requirements. Each revision is versioned and timestamped so that the evolution of the concept remains traceable.
Execution
Step 1 – Load the concept file
Check whether the user named a file:
- If yes: read it completely.
- If no: search the
docs/concepts/directory for concept files and display a compact selection list:"Which concept should be updated? [List of found files with title and current version]"
Wait for the selection before continuing.
Step 2 – Clarify reason for change & context
Check whether the user has already described in the initial prompt what has changed or what should be updated.
If not sufficiently described, ask once briefly:
"What has changed or should be re-evaluated? (e.g. clarified tech stack decision, new scope, changed requirement)"
If the user also named an input file with new notes or decisions: read it as well and process it as context.
Step 3 – Parallel analysis by sub-agents
Start three sub-agents in parallel using the Task tool.
Each agent receives both the existing concept and the change context.
Ambiguities are marked as [UNCLEAR: ...] – do not make assumptions.
Sub-Agent A – What changes in content?
- Which sections of the concept are affected by the change?
- What specifically needs to be reformulated or added?
- Are there contradictions with the existing concept that need to be resolved?
Sub-Agent B – Impact on scope & open questions
- Does the change affect the scope (In Scope / Out of Scope)?
- Which previously open questions from Chapter 5 are now answered?
- Do the changes create new open questions or dependencies?
Sub-Agent C – Impact on risks & next steps
- Does the change alter the risk assessment?
- Do risks fall away, do new ones arise?
- What are the updated next steps?
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.
- today Changed · +3 lines 8c866749999f
- 3d ago First seen · 163 lines · 0 tokens per session scan A 89171df1e09d
konzept-update is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,398 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-31.
Other commands, from other repositories
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
pseo-init
Use when: kullanıcı "yeni proje", "init", "proje kur", "yeni domain ekle", "scaffold" gibi ifadeler kullanır ya da /pseo-init çağırırsa. Also use when: portföye yeni bir SEO projesi alındı, projects/{slug}/ klasörü ve project.config.json dosyasının schemaya uygun ilk hâli üretilecek; brief'te slug + domain + market…
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.
forge-context-status
Report on current context window usage, cache health, and compaction recommendation. Read-only — does not compact.
CLAUDE
Each subdirectory is one engine verb dispatched by ../cli/cli.ts: / .ts exports a pure handler that resolves the vault, does its work through ../core/ primitives, and returns its own typed report. Commands stay thin — they compose core checks and builders; they do not reimplement them. The canonical output schema is…