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 edobreque/clens --skill journey-reportgit clone --depth 1 https://github.com/edobreque/clensWrote 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/edobreque/clens/journey-report)<a href="https://agentmods.dev/skills/edobreque/clens/journey-report"><img src="https://agentmods.dev/badge/skills/edobreque/clens/journey-report/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/edobreque/clens/journey-report"><img src="https://agentmods.dev/badge/skills/edobreque/clens/journey-report.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.00010 | $0.01916 |
| Opus 5 | $0.00005 | $0.00958 |
| Sonnet 5 | $0.00002 | $0.00383 |
| Haiku 4.5 | $0.00001 | $0.00192 |
Grade A, and why
journey-report 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.
This is a copy
100% identical to journey-report — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey Report
Generate a structured lifecycle report for a cross-session development journey.
Variables
TARGET: $ARGUMENTS
Instructions
1. Resolve the Journey
Journey data is built by reading and chaining distilled sessions. There is no standalone clens journey command — journey analysis is done by reading distilled session files directly.
- List all distilled sessions:
ls .clens/distilled/*.json(sorted by modification time) - Read each distilled JSON to extract:
session_id,start_time,stats,summary,user_messages,plan_drift - Chain sessions into a journey:
- Sessions sharing the same working directory and started within 5 seconds of a
/clearor compact event belong to the same journey - Order phases chronologically by
start_time
- Sessions sharing the same working directory and started within 5 seconds of a
- If TARGET is a session ID prefix, find the journey containing that session
- If TARGET is empty or
--last, use the most recent journey (by latest session start time)
If fewer than 1 distilled session exists, tell the user:
No distilled sessions found. Run
clens distill --lastto distill your sessions first.
2. Build the Journey
- Load the
session-analysisskill for schema and interpretation context - For each session in the journey, classify its phase type from the first user prompt:
/prime→prime,/brainstorm→brainstorm,/planor/plan_w_team→plan,/build→build,/review→review,/test→test- "commit" keyword →
commit - High read:write ratio (>3:1) →
exploration -
3 TaskCreate calls (4+) →
orchestrated_build - <30s and <15 events →
abort - Default →
freeform
- Determine
lifecycle_typefrom the set of phase types present:- Has prime + plan + build →
prime-plan-build - Has prime + build (no plan) →
prime-build - Has build (no prime) →
build-only - Single session →
single-session - Otherwise →
ad-hoc
- Has prime + plan + build →
- Compute cumulative stats by summing across all sessions
- Key fields to present:
id,lifecycle_type,phases,transitions,cumulative_stats,plan_drift,spec_ref
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 · 168 lines · 10 tokens per session scan A 0a2a5e55290c
journey-report is a skill published in the GitHub repository edobreque/clens (2 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 1,916 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to journey-report, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
backtrack-analysis
Deep-dive into backtracking patterns from distilled clens sessions.
journey-report
Analyze cross-session development lifecycle and generate a journey report.
session-compare
Compare two distilled clens sessions side-by-side to identify performance differences.
session-report
Analyze a distilled clens session and generate a structured performance report.
session-analysis
Schema knowledge and interpretation guide for clens distilled session data. Auto-loads when reading .clens/distilled/ files.
trulens-evaluation-setup
Configure feedback functions and selectors for TruLens evaluations.