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 Arcadi4/nerdy --skill parallel-algorithmsgit clone --depth 1 https://github.com/Arcadi4/nerdyWrote 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/arcadi4/nerdy/parallel-algorithms)<a href="https://agentmods.dev/skills/arcadi4/nerdy/parallel-algorithms"><img src="https://agentmods.dev/badge/skills/arcadi4/nerdy/parallel-algorithms/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/arcadi4/nerdy/parallel-algorithms"><img src="https://agentmods.dev/badge/skills/arcadi4/nerdy/parallel-algorithms.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.00049 | $0.03324 |
| Opus 5.5 | $0.00020 | $0.01330 |
| Sonnet 5.5 | $0.00010 | $0.00665 |
| Haiku 4.5 | $0.00005 | $0.00332 |
Grade A, and why
parallel-algorithms 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 1mo 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 — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Algorithms
Overview
Core principle: analyze correctness before speed. A fork-join keyword says work may run in parallel; it does not prove race freedom, useful speedup, or production scalability.
Shared CLRS Conventions
Use the parent clrs skill for mathematical formatting, theorem tone, and answer discipline. Keep every bound, recurrence, ratio, and inequality in display LaTeX blocks. Keep Markdown tables verbal; put the formulas in nearby display blocks.
Output Discipline for Parallel Answers
Parallel-algorithm answers are notation-heavy, so formatting leaks are common. Do not announce that this skill is being used. Start with the review or solution.
Use prose names in sentences and tables, then put the notation in display blocks. For example, say "the work is quadratic" in prose, then show the bound below in a display block. Do not put work/span symbols, processor-count formulas, slackness ratios, or asymptotic bounds in table cells, headings, inline math, or inline code spans.
When a table needs a formula, write a verbal label in the cell, such as "quadratic work" or "polylogarithmic span," and put the exact expression immediately after the table.
Arithmetic is also a formula. Processor estimates such as a work term divided by a processor count plus a span term must be displayed in LaTeX blocks, not written as prose-line arithmetic with +, =, /, ÷, powers, or asymptotic notation.
Safe pattern:
The estimate for the first candidate is below.
$$
\frac{2048}{512} + 1 = 5
$$
The estimate for the second candidate is below.
$$
\frac{1024}{512} + 8 = 10
$$
Unsafe pattern:
Version A: 2048 / 512 + 1 = 5 seconds.
When to Use
Use this skill for:
- fork-join pseudocode using
spawn,sync, orparallel for; - serial projection, trace DAGs, strands, critical paths, and sequential consistency;
- work, span, speedup, parallelism, slackness, and greedy scheduling analysis;
- determinacy race reviews and shared-memory update patterns;
- parallel loops, matrix-vector multiplication, matrix multiplication, Strassen, parallel merge, and parallel merge sort;
- parallel reductions, scans, stencils, and randomized parallel algorithms;
- production reviews of textbook parallel algorithms, task granularity, scheduler overhead, work stealing, and coarsening.
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.
- 1mo ago First seen · 397 lines · 49 tokens per session scan A b30d99f442e2
parallel-algorithms is a skill published in the GitHub repository Arcadi4/nerdy (6 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 3,324 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-31.
Other skills, from other repositories
algo-sensei
Your personal DSA & LeetCode mentor. Use for problem explanations, progressive hints, code reviews, mock interviews, pattern recognition, complexity analysis, and custom problem generation. Automatically adapts to your learning style and request type.
coding-frameworks
Reference frameworks for coding interviews — the UMPIRE method, a pattern taxonomy (two-pointers, sliding-window, BFS/DFS, backtracking, dynamic-programming, graphs, and more), a Big-O cheatsheet, Python idioms, communication guidance, and anti-patterns. Used by the coding commands (/coding-explain, /practice-coding…
behavioral-frameworks
Reference frameworks (STAR, SBI, CARL), anti-patterns, and standard interviewer follow-ups for behavioral interview prep. Use when extracting STAR stories from user's experience, mapping stories to a specific company or JD, running mock behavioral interviews, rehearsing behavioral story delivery, or debriefing a real…
nerd
Explains any code, system, or flow as ASCII flowcharts that expose the fundamental data structures and algorithms underneath. Use /skill:nerd to get a bird's-eye-view map of how something works, then zoom into any specific algorithm or data structure for a deeper breakdown. Strips jargon, shows the actual machine …
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…