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 ytunahankskn/oh-meine-excode --skill parallel-sweepgit clone --depth 1 https://github.com/ytunahankskn/oh-meine-excodeWrote 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/ytunahankskn/oh-meine-excode/parallel-sweep)<a href="https://agentmods.dev/skills/ytunahankskn/oh-meine-excode/parallel-sweep"><img src="https://agentmods.dev/badge/skills/ytunahankskn/oh-meine-excode/parallel-sweep.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.00031 | $0.00246 |
| Opus 5 | $0.00015 | $0.00123 |
| Sonnet 5 | $0.00006 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
parallel-sweep 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 8d 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
Parallel Sweep
Use this skill when the task is a broad cleanup or repair pass and the work can be split by file group, feature area, or error class.
Good Targets
- TypeScript error sweeps
- lint cleanup across separate modules
- repetitive API migration work
- broad test repair in disjoint areas
Split Strategy
Prefer one of these:
- by directory
- by feature module
- by error family
Avoid splitting shared foundational files across multiple workers.
Recommended Workflow
- Run the failing command locally to see the error surface.
- Cluster errors into disjoint work buckets.
- Keep the shared or highest-risk bucket local.
- Spawn
workeragents for independent buckets. - Integrate and rerun the command.
- Repeat until the sweep is complete or the remaining failures collapse to one root cause.
Verification
- Always rerun the original failing command after integrating worker results.
- If a worker changed tests or configuration, check for regressions outside its bucket.
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.
- 8d ago First seen · 40 lines · 31 tokens per session scan A 68333b1b8433
parallel-sweep is a skill published in the GitHub repository ytunahankskn/oh-meine-excode (2 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 246 once invoked, about $0.0002 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
fix
Polymorphic iterative repair loop — accept a verifier failure, structured findings (review/resolve/triage-issue), or a bug description; modify→verify→keep on green, auto-revert on guard regression, until clean or iteration cap. Use when the user says "fix", "make it pass", or "apply the findings", or hands an artifact…
srgn-cli
Build safe, syntax-aware srgn CLI commands for source-code search and transformation. Use for srgn commands, scoped refactors (comments/docstrings/imports/functions), multi-file rewrites with --glob, tree-sitter queries, or CI checks with --fail-any/--fail-none.
code-intelligence-contract
Use when dependency, call-chain, blast-radius, architecture, domain-flow, or unfamiliar-codebase analysis needs an optional vendor-neutral code-intelligence provider.
ast-grep
Code search, analysis, and refactoring using ast-grep (sg). Use for AST-based code modifications, structural search, and linting.
qa
Conversational QA mode — user reports bugs in plain language, agent clarifies minimally, files GitHub issues that survive refactors. Trigger on "QA", "QA session", or ad-hoc bug reporting without a fixed deliverable shape. Distinct from branch-scoped and PR-scoped review.
check-sentinel-setup
Run an offline Sentinel package doctor and separate local installation defects from host enablement or Roboflow sign-in problems. TRIGGER when: the user asks to check, verify, diagnose, or troubleshoot a Sentinel plugin installation; run the setup doctor; find missing skills, packaged files, or Roboflow tools; or…