Borrowing it
Nothing to install: this file belongs to foxzool/openlark. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/foxzool/openlark/main/.cursor/skills/verify-openlark/SKILL.mdgit clone --depth 1 https://github.com/foxzool/openlarkWrote 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/foxzool/openlark/verify-openlark)<a href="https://agentmods.dev/skills/foxzool/openlark/verify-openlark"><img src="https://agentmods.dev/badge/skills/foxzool/openlark/verify-openlark/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/foxzool/openlark/verify-openlark"><img src="https://agentmods.dev/badge/skills/foxzool/openlark/verify-openlark.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.00075 | $0.02569 |
| Opus 5.5 | $0.00030 | $0.01028 |
| Sonnet 5.5 | $0.00015 | $0.00514 |
| Haiku 4.5 | $0.00007 | $0.00257 |
Grade A, and why
verify-openlark 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 7d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify OpenLark
OpenLark is a Rust workspace library SDK, not a GUI or long-lived server. Verification means compiling and exercising the SDK the way CI and maintainers do: cargo build/test/fmt/clippy, the feature-combination commands in .github/workflows/ci.yml, public examples (offline unless a live section says otherwise), and the Python harnesses under tools/. Read this skill cold mid-task; follow it literally.
Put control-openlark on PATH for the session:
export PATH="$(pwd)/.cursor/skills/verify-openlark/scripts:$PATH"
# or from anywhere:
export PATH="/absolute/path/to/repo/.cursor/skills/verify-openlark/scripts:$PATH"
Evidence lives under .cursor/skills/verify-openlark/artifacts/<run-id>/ (override with VERIFY_OPENLARK_ARTIFACTS). Cleanup never deletes that tree.
Feature recipes: features/README.md. A proof that drives one convenient entry point is incomplete when the map lists others for the change under test.
Launch
There is no daemon to keep alive. Launch = toolchain ready + one workspace build so later drives share a warm target/.
# Optional isolation (recommended when sharing a machine):
export CARGO_TARGET_DIR="/tmp/openlark-verify-$USER-$$"
control-openlark launch --target-dir "$CARGO_TARGET_DIR"
# Ready when the transcript ends with: READY workspace build finished
# Equivalent raw command (CI does not set a separate build step; this is the workspace compile):
# cargo build --workspace --all-features
Teardown is control-openlark cleanup (see Cleanup). Do not leave isolated CARGO_TARGET_DIR trees forever; purge only paths under /tmp/openlark-verify-* via cleanup --purge-target.
If rustc is older than 1.88, upgrade before generating proofs (rustup update stable && rustup default stable). Edition 2024 requires a modern Cargo. CI's CARGO_TOOLCHAIN is stable.
Doctor
Run first whenever anything looks off, and before the first drive of a run:
control-openlark doctor
What ships with it
10 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.
- .gitignore 71 B
- features/api-coverage.md 1.7 KB
- features/api-field-verify.md 2.1 KB
- features/ci-lint.md 2.0 KB
- features/feature-combinations.md 3.7 KB
- features/feishu-live-e2e.md 6.0 KB
- features/public-examples.md 2.7 KB
- features/README.md 3.3 KB
- features/workspace-build-test.md 2.8 KB
- scripts/control-openlark 15 KB
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.
- 7d ago Changed · +28 lines · +9 tokens per session e84a9e9c73e6
- 1mo ago First seen · 132 lines · 66 tokens per session scan A 7452844ed8ff
verify-openlark is a skill published in the GitHub repository foxzool/openlark (108 stars, last pushed 3d ago), licensed Apache-2.0. It adds 75 tokens to every session and 2,569 once invoked, about $0.0003 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-09-15.
Other skills, from other repositories
rust-development
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
rust-testing
Rust testing conventions and frameworks: built-in #[test], integration, and doctest layout plus the cargo-nextest runner and the proptest, insta, criterion, mockall, and rstest ecosystem. Invoke whenever task involves any interaction with Rust tests — writing, running, configuring, or debugging tests in .rs files and…
rust-testing-quality
Use when writing, organizing, or running Rust tests — unit, integration, doc-tests, proptest, criterion benchmarks, or cargo-mutants. Not for CI pipeline wiring (rust-tooling-cicd).
testing-rust
Writes tests following TDD (using cargo test, proptest, and insta) best practices. Use when writing unit tests, integration tests, or property-based tests in Rust.
rust-best-practices
Write, review, refactor, or optimize Rust, including ownership, errors, Tokio, traits, tests, benchmarks, Clippy, and documentation. Excludes other languages and architecture unrelated to Rust idioms.
testing
Rust testing — unit/integration layout, mocking with mockall, async test patterns, property testing, snapshot testing. Use whenever writing or reviewing Rust tests, setting up test infrastructure, choosing mocking strategies, organizing test modules, debugging test failures, or when the user asks about testing…