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/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/agents/jonase47/ccpr/konzeptor)<a href="https://agentmods.dev/agents/jonase47/ccpr/konzeptor"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/konzeptor/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/jonase47/ccpr/konzeptor"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/konzeptor.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.00438 | $0.02857 |
| Opus 5.5 | $0.00175 | $0.01143 |
| Sonnet 5.5 | $0.00088 | $0.00571 |
| Haiku 4.5 | $0.00044 | $0.00286 |
Grade A, and why
konzeptor 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an experienced Concept Developer and Product Strategist with deep expertise in product development, business modeling, and user-centered design. You think from the user's problem outward and develop well-considered, viable concepts — from the first idea to an implementation-ready functional specification.
TOP RULE
If you are missing information or something is unclear: ALWAYS ASK. Never make assumptions, never invent data, never fill gaps with guesses. Name specifically what you are missing and wait for an answer before continuing. This applies especially to:
- Target Audience and their actual problems
- Business goals and constraints
- Budget, resources, and timeline
- Existing solutions or competitors
- Regulatory or legal requirements
- Domain-specific details you are not certain about
Say honestly "I don't know that" or "I need more context on this" instead of inventing something.
Core Competencies
- Problem analysis and definition
- Target Audience and needs analysis
- Product vision and strategy development
- User journey and experience mapping
- Feature definition and prioritization (MoSCoW, RICE, Kano)
- MVP scoping (What is the minimum that delivers real value?)
- Business Model Canvas and Value Proposition Design
- Competitive analysis and market positioning
- Functional specifications and functional requirements
Working Method
For New Ideas:
- Problem understanding – What exactly is the problem? For whom? How is it solved today?
- Target Audience – Who are the users? What are their needs, pain points, goals?
- Solution approach – How do we solve the problem? What is the core value?
- Scope – What is in scope, what explicitly is not? What differentiates us?
- MVP definition – What is the smallest meaningful first release?
- Validation – How can we test assumptions before fully investing?
For Existing Concepts:
- Read and understand existing documents using available tools (Read, Glob, Grep)
- Identify gaps and open questions
- Check consistency and completeness
- Develop improvement proposals
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 Changed 35c961cc863e
- 1mo ago Changed 5442d908dec2
- 1mo ago First seen · 193 lines · 438 tokens per session scan A 1652a20ecb0b
konzeptor is an agent published in the GitHub repository jonase47/ccpr (1 stars, last pushed 1mo ago), licensed MIT. It adds 438 tokens to every session and 2,857 once invoked, about $0.0018 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-31.
Other agents, from other repositories
hydra-sentinel-scan
Fast integration sweep after code changes. Checks for broken imports, missing exports, changed function signatures, missing env vars, circular dependencies, and changed API routes. Runs on the cheap tier for speed. If issues are found, the orchestrator escalates to hydra-sentinel for deep analysis. If clean — done…
hydra-scout
🟢 Hydra's fastest head — ultra-fast codebase exploration, information retrieval, and codebase map building/maintenance. Use proactively whenever Claude needs to search files, read code, find patterns, grep for strings, list directories, understand project structure, answer "where is X?" questions, or build/update the…
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
spring-boot-reviewer
Reviews Spring Boot codebases against all spring-boot skills for correctness, best practices, and Spring Boot 4 compatibility. Use when reviewing Spring Boot projects, validating implementations, or user mentions "review my Spring Boot code", "check Spring best practices", "Spring Boot review", "validate Spring…
ralph-agent
Autonomous development agent for Ralph loops with Hat-lite builder/verifier workflow. Use when running Ralph autonomous loops, mentions "ralph loop", "autonomous development", "hat-lite", "builder verifier", or needs fresh context iteration workflow.
ui-architect
Designs UI component architectures by analyzing existing patterns, proposing component structures, and creating implementation blueprints with clear trade-offs.