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/konzeptgit clone --depth 1 https://github.com/jonase47/ccprWhat 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.01507 |
| Opus 5 | $0.00000 | $0.00754 |
| Sonnet 5 | $0.00000 | $0.00301 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
konzept 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 2d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/konzept – Create a rough concept for a feature or (sub-)project
Purpose
This command guides through the initial conception phase as a Product Owner. The result is a first structured rough concept that serves as the basis for further steps (user stories, roadmap, stakeholder presentation).
Execution
Step 1 – Clarify context & output format
Input:
- If a file was mentioned: read it completely.
- If only a short description is available: work with it.
- If both are missing: ask once briefly:
"Describe the idea briefly or give me a file with your notes – then I'll get started."
Output format: Check whether the user specified a desired format in the initial prompt.
If no format was specified, ask once:
"How should the result be delivered? (a) Save as a Markdown file in the project folder (b) Output directly in the terminal (c) Both"
Wait for the answer before continuing. If a format was clearly specified, skip this question.
Step 2 – Parallel analysis by sub-agents
Start three sub-agents in parallel using the Task tool.
Each sub-agent should explicitly mark missing or unclear information in their area
(e.g. [UNCLEAR: ...]), but not yet make assumptions – that is handled in Step 3.
Sub-Agent A – Problem space & value
- What problem is being solved? For whom?
- What is the concrete benefit / added value?
- Why is this topic relevant now?
- What alternatives or workarounds exist today?
Sub-Agent B – Scope & boundaries
- What is in scope (core of the solution)?
- What is deliberately out of scope?
- Which systems, interfaces, or dependencies are affected?
- First rough size estimate: Small / Medium / Large?
Sub-Agent C – Risks & open questions
- What critical ambiguities exist?
- What needs to be validated before moving forward?
- What risks or blockers might arise?
- Which open questions need clarification (internal / external)?
Step 2b – Consolidation by Wingman
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.
- 2d ago First seen · 194 lines · 0 tokens per session scan A 47c58a802646
konzept is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,507 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
research
Research a technical or product question.
status
Show Hydra framework status — installed agents, version, config, and update availability.
help
Show everything the Obsidian Knowledge Agent can do, with every command and an example.
clean-check
Analyze code for cleanliness issues (unused code, comment quality, formatting, naming, complexity). Delegates to the code-cleanliness agent.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.