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/rust-works/succinctly/bit-optimizationnpx skills add rust-works/succinctly --skill bit-optimizationgit clone --depth 1 https://github.com/rust-works/succinctlyWhat 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 | $0.00053 | $0.02577 |
| Opus 5 | $0.00026 | $0.01288 |
| Sonnet 5 | $0.00011 | $0.00515 |
| Haiku 4.5 | $0.00005 | $0.00258 |
Grade A, and why
bit-optimization 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 2d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bit-Level Optimization Patterns
Learnings from optimizing succinct data structure operations.
Comprehensive documentation: See docs/optimizations/ for full technique reference:
- bit-manipulation.md - Popcount, CTZ, PDEP/PEXT
- lookup-tables.md - Byte-level lookup tables
- hierarchical-structures.md - Rank/select indices
Byte-Level Lookup Tables
When to use: Scanning bits one-at-a-time is slow (64 iterations per word). Use 256-entry lookup tables to process 8 bits at once.
Pattern: Two-Level Lookup
// Precompute at compile time
const BYTE_MIN_EXCESS: [i8; 256] = { /* min prefix sum for each byte value */ };
const BYTE_TOTAL_EXCESS: [i8; 256] = { /* total excess (popcount*2 - 8) */ };
const BYTE_FIND_CLOSE: [[u8; 16]; 256] = { /* 2D: byte_value x initial_excess */ };
fn find_close_in_word_fast(word: u64, initial_excess: i32) -> Option<usize> {
let bytes = word.to_le_bytes();
let mut excess = initial_excess;
for (i, &byte_val) in bytes.iter().enumerate() {
// Level 1: Can the result be in this byte?
let min_excess_in_byte = BYTE_MIN_EXCESS[byte_val as usize] as i32;
if excess + min_excess_in_byte <= 0 {
// Level 2: Find exact position within byte
if excess <= 16 {
let match_pos = BYTE_FIND_CLOSE[byte_val as usize][(excess - 1) as usize];
return Some(i * 8 + match_pos as usize);
}
// Fallback for excess > 16: bit-by-bit scan of this byte only
}
excess += BYTE_TOTAL_EXCESS[byte_val as usize] as i32;
}
None
}
Key Insights
- Two-level lookup: First check if result is in this byte (fast), then find exact position
- Compile-time computation: Use
constblocks for zero runtime overhead - Hierarchical skip: Skip entire bytes/words when result can't be there
- Fallback for edge cases: Handle out-of-range lookup indices with bit scan
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.
- 2d ago First seen · 262 lines · 53 tokens per session scan A c0020b3061e3
bit-optimization is a skill published in the GitHub repository rust-works/succinctly (51 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 2,577 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…