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 02loveslollipop/OpenCROW --skill opencrow-crypto-toolboxgit clone --depth 1 https://github.com/02loveslollipop/OpenCROWWrote 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/02loveslollipop/opencrow/opencrow-crypto-toolbox)<a href="https://agentmods.dev/skills/02loveslollipop/opencrow/opencrow-crypto-toolbox"><img src="https://agentmods.dev/badge/skills/02loveslollipop/opencrow/opencrow-crypto-toolbox/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/02loveslollipop/opencrow/opencrow-crypto-toolbox"><img src="https://agentmods.dev/badge/skills/02loveslollipop/opencrow/opencrow-crypto-toolbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.00961 |
| Opus 5 | $0.00039 | $0.00481 |
| Sonnet 5 | $0.00016 | $0.00192 |
| Haiku 4.5 | $0.00008 | $0.00096 |
Grade A, and why
opencrow-crypto-toolbox 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 9d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCROW Crypto Toolbox
Runtime preflight
Probe required commands with command -v and Python modules with importlib.util.find_spec before use. Prefer a PATH-resolved OpenCROW MCP helper or the ctf/sage environment when available, then the managed helper or system Python. If a capability is missing, stop that path safely and report the exact missing command or module.
Prefer the opencrow-crypto-mcp server for typed crypto workflows. Fall back to the direct scripts only when you need to debug the underlying ctf-environment execution path.
MCP First
- Use
toolbox_info,toolbox_verify, andtoolbox_capabilitiesfirst. - Use the typed crypto operations:
crypto_pythoncrypto_factordb_lookupcrypto_crack_hash
- Treat the existing helper scripts as the implementation fallback, not the primary interface.
Use this skill for Python-first crypto work in the ctf environment plus the cracking and lookup tools that commonly complement it. This covers SMT constraints with z3, lattice work with fpylll, implementation helpers with pycryptodome, offline cracking with hashcat or john, and quick FactorDB checks.
Quick Start
Run inline Python in ctf:
python3 scripts/run_crypto_python.py --code 'from z3 import *; x = BitVec("x", 32); s = Solver(); s.add(x ^ 0x1337 == 0x1234); print(s.check()); print(s.model())'
Run a solver file:
python3 scripts/run_crypto_python.py --file /absolute/path/to/solve.py
Verify the mapped stack:
python3 scripts/verify_toolkit.py
Query FactorDB quickly:
python3 scripts/factordb_lookup.py 999630013489
Workflow
- Use this toolbox when the job is mostly Python, constraints, lattices, or byte-level crypto helpers.
- Use
run_crypto_python.py --codefor short experiments and--filefor real solve scripts. - Reach for
z3when the challenge is equation- or bit-vector-driven. - Reach for
fpylllwhen the attack is lattice-driven and does not require Sage. - Reach for
pycryptodomewhen you need standard primitives, block modes, or protocol glue in Python. - Reach for
hashcatorjohnwhen the fastest path is cracking rather than symbolic recovery. - Read references/tooling.md if you need a quick selection guide.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 78 lines · 78 tokens per session scan A e89416f8d024
opencrow-crypto-toolbox is a skill published in the GitHub repository 02loveslollipop/OpenCROW (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 78 tokens to every session and 961 once invoked, about $0.0004 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
goga-cell-python
Python rules for implementing CODEMANIFEST contracts.
goga-lang-disp
Detects the project language and dispatches execution to the matching language-specific skill. Apply this specification within the calling skill's context. Do not restate the contents — use them for decision-making.
python-package-management
Guide for managing packages in the Agent Framework Python monorepo, including creating new connector packages, versioning, and the lazy-loading pattern. Use this when adding, modifying, or releasing packages.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.