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 easyzoom/aix-skills --skill crc-checksum-integrationgit clone --depth 1 https://github.com/easyzoom/aix-skillsWrote 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/easyzoom/aix-skills/crc-checksum-integration)<a href="https://agentmods.dev/skills/easyzoom/aix-skills/crc-checksum-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/crc-checksum-integration/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/easyzoom/aix-skills/crc-checksum-integration"><img src="https://agentmods.dev/badge/skills/easyzoom/aix-skills/crc-checksum-integration.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.00036 | $0.00650 |
| Opus 5 | $0.00018 | $0.00325 |
| Sonnet 5 | $0.00007 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
crc-checksum-integration 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 11d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRC Checksum Integration
Overview
Use this skill to integrate CRCs and checksums by making the exact algorithm parameters explicit. Most CRC bugs come from two sides using the same name for different init, reflection, xorout, byte order, or covered range.
When To Use
Use this skill when:
- The user needs CRC-8, CRC-16, CRC-32, additive checksum, Fletcher, Adler, or protocol frame validation.
- The issue involves mismatched CRC values, boot image validation, Modbus, CAN, UART packets, storage records, or OTA packages.
- The target uses hardware CRC units, DMA, endian-sensitive protocols, or streaming updates.
Do not use this skill for cryptographic authentication. Use mbedtls-integration, tinycrypt-integration, or micro-ecc-integration when adversarial tampering matters.
First Questions
Ask for:
- Algorithm name plus polynomial, width, init, refin, refout, xorout, and check value if known.
- Exact byte range covered, header/trailer inclusion, padding, and endian order.
- Whether the implementation is table-driven, bitwise, hardware accelerated, or streaming.
- Known-good sample input and expected output from the peer device or specification.
- Current mismatch and where it is observed.
Integration Checklist
-
Write the full CRC tuple. Do not rely on names like CRC-16 unless the parameters are specified.
-
Verify with a golden vector. Test
123456789or a protocol-provided frame before using live data. -
Freeze byte coverage. Define start offset, length, skipped fields, padding, escaping, and final byte order.
-
Match streaming behavior. The incremental API must preserve state exactly across chunks and resets.
-
Compare hardware and software. Hardware CRC units often need byte reversal, word packing, or final xor handling.
-
Add negative tests. Flip one bit in payload and metadata to prove the check actually fails.
Common Failures
- Wrong reflection settings for the named CRC variant.
- Including the CRC field itself in the covered range.
- Feeding words into a hardware CRC in host endian instead of wire order.
- Using a checksum where collision resistance or authenticity is required.
- Resetting incremental CRC state between chunks.
- Comparing printed hex values with opposite byte 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.
- 11d ago First seen · 84 lines · 36 tokens per session scan A 6ae1ec99164b
crc-checksum-integration is a skill published in the GitHub repository easyzoom/aix-skills (31 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 650 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-30.
Other skills, from other repositories
container-home
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Investigate bugs and errors in Elixir/Phoenix — root-cause analysis for crashes, exceptions, stack traces, test failures. Use --parallel for deep 4-track investigation.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.