Borrowing it
Nothing to install: this file belongs to dealfluence/adeu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dealfluence/adeu/main/.opencode/skills/analyze-branching/SKILL.mdgit clone --depth 1 https://github.com/dealfluence/adeuWrote 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/dealfluence/adeu/analyze-branching)<a href="https://agentmods.dev/skills/dealfluence/adeu/analyze-branching"><img src="https://agentmods.dev/badge/skills/dealfluence/adeu/analyze-branching/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/dealfluence/adeu/analyze-branching"><img src="https://agentmods.dev/badge/skills/dealfluence/adeu/analyze-branching.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00260 |
| Opus 5.5 | $0.00013 | $0.00104 |
| Sonnet 5.5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
analyze-branching 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 2mo 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
Analyze Branching Skill
This skill provides formal analysis of control-flow branchings, decision points, and nesting depth across the Python (python/src/adeu/redline/engine.py) and TypeScript (node/packages/core/src/engine.ts) engine implementations.
Usage
Run the engine branch checker script from repository root:
uv run python scripts/check_engine_branches.py
Or analyze individual files:
Python Analysis
uv run python scripts/analyze_python_branches.py [path_to_file]
TypeScript Analysis
node scripts/analyze_ts_branches.mjs [path_to_file]
Metrics
- Cyclomatic Complexity: Counts decision nodes (
if,elif/else, loops, exception handlers, logical boolean operatorsand/or/&&/||, conditional expressions). - Max Depth: Deepest nesting level of control flow structures inside a single function.
- Deep Nesting Warning: Flags functions with branch nesting levels $\ge 6$.
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.
- 2mo ago First seen · 34 lines · 33 tokens per session scan A b2ed1995df8a
analyze-branching is a skill published in the GitHub repository dealfluence/adeu (169 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 260 once invoked, about $0.0001 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-30.
Other skills, from other repositories
lsp-mcp-server
Use with Codex, Claude Code, or another MCP client when lsp-mcp-server is connected and semantic code navigation, analysis, refactoring, or diagnostics are needed. Covers all 29 lsp tools for TypeScript, Python, Rust, Go, C/C++, Ruby, PHP, Elixir, Kotlin, Java, and user-configured languages. Prefer these tools to text…
lain
Structural code intelligence for AI coding agents. Use this skill when the user wants to understand how a codebase is organized (modules, call graphs, file dependencies), find where to start reading, trace the impact of a change, find code by meaning, or understand what a symbol does in its full context. Do NOT use…
explore
Build an accurate mental model of an unfamiliar codebase, feature, or area before changing it — where it lives, how it connects, what it does, and why. Use when asked how something works, where something is, when onboarding to a repo, or before editing code you don't know. For a cross-cutting question that needs…
debug
Trace a bug, error, or regression to its root cause. Use when investigating a failure, a stack trace, unexpected behavior, or "why does X happen".
lain-architecture
Use for system-shape questions through Lain — "map this subsystem", "compare these modules", "trace the dependency chain", "how deep is this in the stack", "where is the god object", "run a raw graph query". Covers the arch and raw packages.
lain-comprehension
Use when reading, locating, or assessing code through Lain's MCP tools — "where is X", "explain this", "what breaks if I change this", "what should I read first", "is this answer trustworthy". Covers the default core surface and the honest-answer contract.