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/hamzapixl/pixl-ai/batchnpx skills add hamzaPixl/pixl-ai --skill batchgit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/batch)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/batch"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/batch.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.1 | $0.00050 | $0.01303 |
| Opus 5 | $0.00025 | $0.00651 |
| Sonnet 5 | $0.00010 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
batch 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Parallel worktree execution engine. Takes a transformation (refactor, migration, code mod, style change) and a target scope (files, modules, services), decomposes into N independent units, executes each in its own git worktree via isolated agents, then merges results.
Why worktree isolation matters: Each agent gets its own copy of the repo. No file conflicts during execution. Merge conflicts only surface at the explicit merge step — where they can be resolved intelligently instead of causing mid-execution failures.
Step 1: Analyze Scope
Identify the transformation and target scope:
- Parse the user's description to extract:
- Transformation: What change to apply (e.g., "migrate from Jest to Vitest", "add error boundaries to all pages")
- Target scope: Which files/modules to transform (e.g.,
src/modules/*/,**/*.test.ts)
- Scan the target scope with Glob/Grep to enumerate candidate files
- Verify each candidate is a valid transformation target
Step 2: Decompose
Split the scope into N independent units (max 10):
- Group files by natural boundaries (module, directory, feature area)
- Verify independence — units must NOT share files (a file belongs to exactly one unit)
- For each unit, define:
- Files: List of files in this unit
- Prompt: Focused transformation instruction for this unit
- Success criteria: How to verify the transformation worked (tests pass, type-checks, lint clean)
Present the decomposition table to the user:
Unit | Files | Description
-----|-------------|------------------------------------------
1 | src/auth/* | Migrate auth module tests from Jest to Vitest
2 | src/billing/*| Migrate billing module tests from Jest to Vitest
...
Ask for confirmation before proceeding. The user may adjust units, exclude files, or modify the transformation.
Step 3: Execute in Parallel
Spawn up to 10 agents in parallel, each with isolation: "worktree":
For each unit:
Agent(
isolation: "worktree",
prompt: "Transform these files: [file list]. Apply: [transformation]. Success: [criteria]. Do NOT modify files outside your scope."
)
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.
- 6d ago First seen · 128 lines · 50 tokens per session scan A 8b7832569d61
batch is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,303 once invoked, about $0.0003 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
将 Comet GitHub 维护请求路由到基于证据的 PR 审阅、Issue 分诊、本地想法收集、CI 诊断或 Issue 实施流程。用户提到 Comet GitHub Issue/PR 但未指定流程,或询问下一步如何处理时使用。.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".