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 lttr/claude-marketplace --skill feature-branchgit clone --depth 1 https://github.com/lttr/claude-marketplaceWrote 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/lttr/claude-marketplace/feature-branch)<a href="https://agentmods.dev/skills/lttr/claude-marketplace/feature-branch"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/feature-branch/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/lttr/claude-marketplace/feature-branch"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/feature-branch.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.00074 | $0.00504 |
| Opus 5 | $0.00037 | $0.00252 |
| Sonnet 5 | $0.00015 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
feature-branch 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 11d 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
Feature Branch
Create feature/<ticket-id>-<slug> from an Azure DevOps work item.
Input Detection
Argument is $ARGUMENTS.
| Form | Meaning |
|---|---|
| empty | look in recent context for ticket; else ask |
numeric (12345) |
ticket id, fetch title for slug |
URL containing _workitems/edit/<id> |
extract id, fetch title |
<id> <slug-override> |
use override slug, skip title fetch |
Workflow
1. Resolve ticket + slug
empty
Scan recent conversation for work item id + title (e.g. prior triage output). Else ask user.
id / URL
az boards work-item show --id <id> --query "{id:id,title:fields.\"System.Title\"}" -o json
Slugify title: lowercase, strip special chars, spaces→hyphens, 3–5 words max.
<id> <override>
Use override directly. Slugify same rules.
2. Pre-flight
git status --short
If dirty → warn, ask: stash / abort.
git branch --show-current
Note current branch (return point).
3. Create branch
git checkout -b feature/<id>-<slug>
If branch already exists → switch to it instead, inform user.
4. Optional: transition ticket → Active
Prompt: "Transition ticket # to Active? (y/N)"
Default: No.
If yes → invoke ticket skill with <id> active.
5. Confirm
Print created branch name + ticket transition status.
Notes
- Branch and ticket transition are intentionally separate —
feature-branchonly prompts; clean separation. - For follow-up state changes use
ticketskill (/dev-azdo:ticket <id> cr, etc.).
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.
- 11d ago First seen · 79 lines · 74 tokens per session scan A aa5d4359093d
feature-branch is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 504 once invoked, about $0.0004 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
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
check-bin-obj-clash
Detects MSBuild projects with conflicting OutputPath or IntermediateOutputPath. USE FOR: builds failing with 'Cannot create a file when that file already exists', 'The process cannot access the file because it is being used by another process', intermittent build failures that succeed on retry, or missing/overwritten…
build-perf-diagnostics
Diagnose MSBuild build performance bottlenecks using binary log analysis. USE FOR: identifying why builds are slow by analyzing binlog performance summaries, detecting ResolveAssemblyReference (RAR) taking >5s, Roslyn analyzers consuming >30% of Csc time, single targets dominating >50% of build time, node utilization…
dump-collect
Configure and collect crash dumps for modern .NET applications. USE FOR: enabling automatic crash dumps for CoreCLR or NativeAOT, capturing dumps from running .NET processes, setting up dump collection in Docker or Kubernetes, using dotnet-dump collect or createdump. DO NOT USE FOR: analyzing or debugging dumps…
binlog-generation
Generate MSBuild binary logs (binlogs) for build diagnostics and analysis. USE FOR: adding /bl:{} to any dotnet build, test, pack, publish, or restore command to capture a full build execution trace, prerequisite for binlog-failure-analysis and build-perf-diagnostics skills, enabling post-build investigation of errors…
binlog-failure-analysis
Analyze MSBuild binary logs to diagnose build failures. USE FOR: build errors that are unclear from console output, diagnosing cascading failures across multi-project builds, tracing MSBuild target execution order, and generally any MSBuild build issues. Requires an existing .binlog file. DO NOT USE FOR: generating…