Borrowing it
Nothing to install: this file belongs to LedgerHQ/ledger-live. 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/LedgerHQ/ledger-live/develop/.agents/skills/batch-feature-dev/SKILL.mdgit clone --depth 1 https://github.com/LedgerHQ/ledger-liveWrote 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/ledgerhq/ledger-live/batch-feature-dev)<a href="https://agentmods.dev/skills/ledgerhq/ledger-live/batch-feature-dev"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/batch-feature-dev/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/ledgerhq/ledger-live/batch-feature-dev"><img src="https://agentmods.dev/badge/skills/ledgerhq/ledger-live/batch-feature-dev.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.00052 | $0.00557 |
| Opus 5.5 | $0.00021 | $0.00223 |
| Sonnet 5.5 | $0.00010 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
batch-feature-dev 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Batch Feature Dev
Deliver ticket batches as coordinated PRs while keeping each ticket scoped and reviewable.
Load First
Read relevant skills before entering their phase:
feature-devper ticket or coupled group.git-conventionsbefore branch, commit, rebase, or push work.create-changesetbefore changesets;create-prfor draft PRs.ldls-nativeorldls-webbefore Lumen UI work.structure-flowbefore placing any code;mvvm-architecturefor the app side inapps/*/src/mvvm/.validate-changesfor validation.
Workflow
- Place the code. Intake every Jira ticket link, description, attachment, mockup, and constraint (fetch details with available Jira/Atlassian tools; ask if anything is inaccessible), then decide with
structure-flowwhich layer and package own each concern of each ticket. Only screens composing@features/*and app-only code go toapps/*/src/mvvm/. Work several tickets need gets one owning package. - Before coding, produce a compact matrix: id/link, area, owning packages, UI impact, tests/screenshots, dependencies, shared work, blockers. Ask consolidated questions for missing mockups, conflicts, unclear copy, APIs, analytics, navigation, flags, and edge cases.
- Branch via
git-conventions. Start unrelated tickets from updateddevelop; chain only for real dependencies, target the previous branch, and state it in the PR. For shared groundwork, prefer one small foundation PR plus dependent PRs. - For each ticket/group, run full
feature-dev, starting from the agreed placement. Treat tickets and mockups as source of truth; ask on conflicts; use Lumen components; add only English source translations; keep shared utilities owned and justified. - Validate affected scope with
validate-changes, plus screenshots or manual visual checks for UI. Add a changeset with exact package names; usecreate-prfor draft PR and Slack message. - Handoff each PR with ticket, branch, target, URL, changeset, validation results, screenshots/status, risks, and follow-ups. After the batch, summarize dependency graph and review order.
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.
- today Changed d5ead18b0303
- 2d ago Changed c20ca8e6cb40
- 2mo ago First seen · 33 lines · 52 tokens per session scan A 5c877a6fad49
batch-feature-dev is a skill published in the GitHub repository LedgerHQ/ledger-live (624 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 557 once invoked, about $0.0002 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
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking, and the required design-impact and area labels. Use when the user says create new issues, report a bug, file a bug, feature request, new…
prepare
Draft release-preparation artefacts for : the planning issue, the version-bump and changelog prep PR (with the first-release review of what the source archive ships), the post-release dev-version bump PR, and, for ASF projects, the one-time automated-signing setup. Every output is a draft the RM confirms; nothing is…
dot-ai-projectSetup
Setup project, audit repository, or generate repository files. Use this when user wants to: setup project, audit repo, check missing files, create README, add LICENSE, generate CONTRIBUTING.md, add CI/CD workflows, initialize documentation, setup governance files. Analyzes local repositories and generates missing…