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 skills/silouone/clens/backtrack-analysisnpx skills add silouone/clens --skill backtrack-analysisgit clone --depth 1 https://github.com/silouone/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/silouone/clens/backtrack-analysis)<a href="https://agentmods.dev/skills/silouone/clens/backtrack-analysis"><img src="https://agentmods.dev/badge/skills/silouone/clens/backtrack-analysis.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.00012 | $0.02015 |
| Opus 5 | $0.00006 | $0.01007 |
| Sonnet 5 | $0.00002 | $0.00403 |
| Haiku 4.5 | $0.00001 | $0.00201 |
Grade A, and why
backtrack-analysis 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- backtrack-analysis — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backtrack Analysis
Deep-dive into backtracking patterns from a distilled clens session. This command focuses entirely on wasted effort: failure retries, iteration struggles, and debugging loops.
Variables
TARGET: $ARGUMENTS
Instructions
1. Resolve the Session
- If TARGET is empty or
--last, find the most recent distilled session:- List files in
.clens/distilled/sorted by modification time - Use the most recently modified
.jsonfile
- List files in
- If TARGET is a session ID (full UUID or prefix), find
.clens/distilled/{TARGET}*.json - If no distilled file is found, tell the user:
No distilled session found. Run
clens distill --lastto distill your most recent session, then re-run this command.
2. Read the Data
- Read the distilled JSON file at
.clens/distilled/{sessionId}.json - Parse the full
DistilledSessionobject - Focus on:
backtracks,file_map,decisions,reasoning,timeline,stats - Load the
session-analysisskill for schema and interpretation context
3. Generate the Analysis
Use the following template. If there are zero backtracks, generate a short clean-execution report instead.
If Zero Backtracks
Backtrack Analysis: {session_id first 8 chars}
No backtracks detected. This session had a clean execution with no detected failure retries, iteration struggles, or debugging loops.
Session stats for context:
- Duration: {summary.key_metrics.duration_human}
- Tool calls: {stats.tool_call_count}
- Failure rate: {stats.failure_rate as %}%
- Files modified: {summary.key_metrics.files_modified}
{If stats.failure_count > 0 but no backtracks: "Note: {failure_count} tool failures occurred but none triggered backtracking patterns. The agent recovered without retrying."}
If Backtracks Exist
Backtrack Analysis: {session_id first 8 chars}
Summary
| Metric | Value |
|---|---|
| Total backtracks | {backtracks.length} |
| failure_retry | {count of type failure_retry} |
| iteration_struggle | {count of type iteration_struggle} |
| debugging_loop | {count of type debugging_loop} |
| Total wasted attempts | {sum of all backtracks' attempts} |
| Time spent backtracking | {sum of (end_t - start_t) for all backtracks, formatted as human duration} |
| % of session in backtracks | {backtrack_time / stats.duration_ms * 100}% |
| Unique files affected | {count of unique file_path values across backtracks} |
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.
- 4d ago First seen · 195 lines · 12 tokens per session scan A 7d69e1c2ce21
backtrack-analysis is a skill published in the GitHub repository silouone/clens (6 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 2,015 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-08-31.
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-analysis
Schema knowledge and interpretation guide for clens distilled session data. Auto-loads when reading .clens/distilled/ files.
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.
effect-and-errors
Composing Effect programs, domain errors, HttpError, repository error types, or error propagation at HTTP boundaries.