clare: Skill for Codex

.codex/skills/clare-env-setup/SKILL.md

clare-env-setup is a skill for Codex from jketreno/clare. It costs 0 tokens per session (606 once invoked), scanned A, original, MIT.

A project setup scanner for CLARE verification. It checks the repository’s languages and configuration files, then reports tools, VS Code extensions, and build or test areas that may need coverage.

In plain words
What is it for?
Use it to inspect a repository, identify required tools, recommend VS Code extensions, review CLARE verification scripts, and optionally update VS Code extension settings or create Dockerfile.clare.
Why use it?
It reduces the time spent figuring out how a project should be checked. It can also create a Dockerfile, which describes an isolated container for repeatable verification runs.

Skill for Codex

Written for Codex: installed under .codex/.

This is jketreno/clare's own configuration. It tells Codex how to work on clare itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything clare configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is ./scripts/clare-installer.sh --target /path/to/project --install-skill "1".

Reuse

Borrowing it

Nothing to install: this file belongs to jketreno/clare. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jketreno/clare/main/.codex/skills/clare-env-setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/jketreno/clare

Made for: Codex.

Wrote 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.

agentmods badge for clare-env-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/jketreno/clare/clare-env-setup/github.svg)](https://agentmods.dev/skills/jketreno/clare/clare-env-setup)
Your own site
<a href="https://agentmods.dev/skills/jketreno/clare/clare-env-setup"><img src="https://agentmods.dev/badge/skills/jketreno/clare/clare-env-setup/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.

agentmods 80×15 button for clare-env-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/jketreno/clare/clare-env-setup"><img src="https://agentmods.dev/badge/skills/jketreno/clare/clare-env-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 606 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00606
Opus 5 $0.00000 $0.00303
Sonnet 5 $0.00000 $0.00121
Haiku 4.5 $0.00000 $0.00061

Measured 8d ago against content hash f290c20a1ba9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 8d 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.

.codex/skills/clare-env-setup/SKILL.md · 50 lines

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.clare to 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.json in 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 (under install/): a suggested, minimal image to run ./clare/verify-ci.sh --fast without 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.clare installs the Go toolchain from the official tarball by default (build-arg GO_VERSION=1.22.9). This enables language checks that require go and binaries installed via go install (for example shfmt) 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-skill flag. You can pass a quoted list of numeric indices (as shown during the setup prompt) or all. 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) with fileCounts, configsFound, verifyTools, recommendedExtensions, detectedSurfaces, verifiedSurfaces, coverageGaps, and agentPrompts sections.

See install/clare/README.md for additional details and examples.

Changes

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.

  1. 8d ago First seen · 50 lines · 0 tokens per session scan A f290c20a1ba9

Subscribe to this mod's changes

clare-env-setup is a skill published in the GitHub repository jketreno/clare (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 606 tokens. 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.

Related

Other skills, from other repositories

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

compute-env-setup

Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.

companion-inc/feynman · 45 tokens

securing-kubernetes-on-cloud

This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…

xalgorix/xalgorix · 80 tokens

detecting-privilege-escalation-in-kubernetes-pods

Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.

xalgorix/xalgorix · 40 tokens

implementing-rbac-hardening-for-kubernetes

Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.

xalgorix/xalgorix · 41 tokens

docker-socket-mount

Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.

PurpleAILAB/Decepticon · 67 tokens