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 skills add jxoesneon/Ciel --skill product-lensgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/skills/jxoesneon/ciel/product-lens)<a href="https://agentmods.dev/skills/jxoesneon/ciel/product-lens"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/product-lens/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/skills/jxoesneon/ciel/product-lens"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/product-lens.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.00018 | $0.00568 |
| Opus 5 | $0.00009 | $0.00284 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
product-lens 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 9d 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.
What it actually says
CIEL ADAPTATION: Product Lens (Discovery & Viability)
This skill formalizes the "Discovery" phase of CIEL development. It asks the hard questions required to validate a feature's "Why" before a single line of code is planned.
Diagnostic Modes
1. The Core 7 Diagnostic
The Orchestrator MUST answer these 7 questions before authorizing a new project:
- Who: Specific user persona.
- Pain: Quantifiable problem being solved.
- Why Now: What technical or market shift makes this possible?
- The 10-Star: The "Unlimited Budget" version of the feature.
- The MVP: Smallest version that proves the core thesis.
- Anti-Goal: What this feature explicitly will NOT do.
- Success Metric: How we will know it works (not vibes).
2. User Journey Audit
For existing features, the Orchestrator MUST:
- Clone/Install as a fresh user.
- Document every friction point and missing doc.
- Time the "Time-to-Value" (TTV).
- Recommend the top 3 friction-reduction fixes.
3. Feature Prioritization (ICE Score)
When choosing between multiple ideas, rank them using:
- Impact (1-5)
- Confidence (1-5)
- Ease (1-5)
- Result: (Impact * Confidence) / Ease.
Output Artifact
Produces a PRODUCT-BRIEF.md containing the diagnosis and a clear GO/NO-GO recommendation.
Anti-Patterns
- Founder-Theater: Building a feature just because it "sounds cool" without defining a success metric.
- Invisible Friction: Ignoring a 5-minute setup hurdle because the developer "already has it installed."
- Scope Creep: Expanding the MVP into the 10-star version before the thesis is proven.
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.
- 9d ago First seen · 68 lines · 18 tokens per session scan A aeaf18a2387a
product-lens is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 18 tokens to every session and 568 once invoked, about $0.0001 per session on Opus 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-09-03.
Other skills, from other repositories
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
ai-native-software-dev
Use when the user asks to build, change, modernize, or reconstruct non-trivial software with an AI-native workflow, including greenfield development, work in an existing codebase, or authorized reference-based product reconstruction; also use when lifecycle planning, architecture, implementation, testing, review…
ticket-spec
Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
redpolicy-guide
An editorial policy for turning webinar transcripts into self-contained guides. A transcript is a written record of spoken material, while a self-contained guide can be understood without watching the webinar.
write-overview
A workflow for researching and writing a review essay about a project topic when no finished source text exists. It gathers the facts, studies example essays when available and produces the article in a project output folder.