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 rules/jketreno/clare/skill-clare-env-setupgit clone --depth 1 https://github.com/jketreno/clareWrote 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/rules/jketreno/clare/skill-clare-env-setup)<a href="https://agentmods.dev/rules/jketreno/clare/skill-clare-env-setup"><img src="https://agentmods.dev/badge/rules/jketreno/clare/skill-clare-env-setup.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.00625 |
| Opus 5 | $0.00005 | $0.00313 |
| Sonnet 5 | $0.00002 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
skill-clare-env-setup 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 5d 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.
What it actually says
CLARE Skill: clare-env-setup
description: Detect project file types, recommend tools and VS Code extensions, and optionally generate Dockerfile.clare for reproducible verification runs.
This skill provides an env-scan helper that inspects a repository, reports which languages and common config files are present, extracts tooling requirements from clare/verify-ci.sh and clare/verify-local.sh, recommends VS Code extensions, and identifies likely deployment/build/test surfaces that still need CLARE coverage.
Purpose
- Help contributors quickly configure their environment for CLARE verification.
- Provide a small
Dockerfile.clareto run verification in an isolated container.
Usage
Installing this skill also installs the scanner into your project at
clare/scripts/clare-env-scan.sh. Run it from the project root:
-
Run the scanner (human-readable report):
bash clare/scripts/clare-env-scan.sh --report
-
Machine-readable JSON output:
bash clare/scripts/clare-env-scan.sh --json > /tmp/clare-scan.json
-
Attempt to update
.vscode/extensions.jsonin the repository (use with care):bash clare/scripts/clare-env-scan.sh --apply-extensions --vscode-dir .vscode
Notes
- The scanner is intentionally conservative and will only auto-apply VS Code recommendations when explicitly requested.
- The CLARE source repo also ships a
Dockerfile.clare(underinstall/): a suggested, minimal image to run./clare/verify-ci.sh --fastwithout polluting the host. Copy it into your project and edit it to add or remove language runtimes as needed.
Dockerfile details
- The CLARE source repo's
install/Dockerfile.clareinstalls the Go toolchain from the official tarball by default (build-argGO_VERSION=1.22.9). This enables language checks that requiregoand binaries installed viago install(for exampleshfmt) to be available inside the container. To override the Go version or skip installation, use--build-arg GO_VERSION=...or an empty value to skip.
Installer usage
- The installer supports non-interactive skill installation with the
--install-skillflag. You can pass a quoted list of numeric indices (as shown during the setup prompt) orall. Example:
./scripts/clare-installer.sh --target /path/to/project --install-skill "1"
./scripts/clare-installer.sh --target /path/to/project --install-skill "all"
Outputs
- Plain text report (default
--report). - JSON (
--json) withfileCounts,configsFound,verifyTools,recommendedExtensions,detectedSurfaces,verifiedSurfaces,coverageGaps, andagentPromptssections.
See install/clare/README.md for additional details and examples.
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.
- 5d ago First seen · 55 lines · 9 tokens per session scan A 1ddbf6858890
skill-clare-env-setup is a cursor rule published in the GitHub repository jketreno/clare (5 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 625 once invoked, about $0.0000 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.