Install Anti-Slop Oxlint Rules
dmmulroy/anti-slop
Installs, updates or migrates the vendored anti-slop Oxlint plugin in a repository, keeping local rule changes and the plugin's license and provenance files.
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
Install Grace CLI
$ npx skills add osovv/grace-marketplace --skill grace-cli -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install osovv/grace-marketplace grace-cli --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grace/grace-cli .claude/skills/grace-cli && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "grace-cli" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-cli into .claude/skills/grace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-cli", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-cliType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add osovv/grace-marketplace --skill grace-cli -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install osovv/grace-marketplace grace-cli --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/grace/grace-cli .agents/skills/grace-cli && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "grace-cli" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-cli into .agents/skills/grace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-cli", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add osovv/grace-marketplace --skill grace-cli -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install osovv/grace-marketplace grace-cli --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/grace/grace-cli .cursor/skills/grace-cli && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "grace-cli" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-cli into .cursor/skills/grace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-cli", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/osovv/grace-marketplace.git --path skills/grace/grace-cli--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add osovv/grace-marketplace --skill grace-cli -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install osovv/grace-marketplace grace-cli --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/grace/grace-cli .gemini/skills/grace-cli && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "grace-cli" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-cli into .gemini/skills/grace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-cli", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install osovv/grace-marketplace grace-cliInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add osovv/grace-marketplace --skill grace-cli -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/grace/grace-cli .github/skills/grace-cli && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "grace-cli" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-cli into .github/skills/grace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-cli", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add osovv/grace-marketplace --skill grace-cli -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install osovv/grace-marketplace grace-cli --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/osovv/grace-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/grace/grace-cli .opencode/skills/grace-cli && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "grace-cli" agent skill from https://github.com/osovv/grace-marketplace/tree/main/skills/grace/grace-cli into .opencode/skills/grace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grace-cli", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
grace-cli- GitHub stars
- 252
- Token cost
- ~1k tokens
- SKILL.md length
- 498 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
- Tasks that involve Linting and formatting
- Calls bun
What it does
Grace CLI is an agent skill from osovv/grace-marketplace. Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Linting and formatting. The repository describes itself as: GRACE (Graph-RAG Anchored Code Engineering): open Agent Skills for contract-driven AI code generation with semantic markup, knowledge graphs, and support for Claude Code, Codex… The licence is MIT.
When your agent uses it
- Tasks that involve Linting and formatting
Example prompts
- “/grace-cli”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 70f5ec4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Grace CLI loads about 1k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 498 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from osovv/grace-marketplace at commit 70f5ec4, republished under its MIT licence (© osovv). 498 words, ~1,009 tokens.
Download SKILL.mdSave it as
.claude/skills/grace-cli/SKILL.md (or your agent's skills folder).- name
- grace-cli
- description
- Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup.
<skill>
<installation_contract>Invoke the installed stable `grace` binary directly. If it is missing, install it with `bun add -g @osovv/grace-cli`. Do not default to `bunx`, `npx`, or the `rc` dist-tag.</installation_contract><commands>
- Active-baseline preflight before observed writes: `grace lint --path PROJECT --assertions current`
- Selected baseline: `grace lint --path PROJECT --change C-ID --assertions baseline` (add `--run-commands` when the baseline declares `MustPassCommand`)
- Selected target: `grace lint --path PROJECT --change C-ID --assertions target --run-commands`
- Final execution gate: `grace lint --path PROJECT --change C-ID --assertions final --run-commands`
- Parallel preflight: `grace lint --path PROJECT --parallel-preflight`
- Status: `grace status --path PROJECT --with modules --json`
- Navigation: `grace module find|show`, `grace verification find|show`, and `grace file show`.
</commands><command_run_contract>
--run-commands executes each declared MustPassCommand value once per lint, fail-fast, with a default 600s per-command timeout (--command-timeout SECONDS overrides, 0 disables). Plan, progress, and per-command result lines go to stderr; the lint report and JSON go to stdout, so piping stdout stays safe. Agents and pipes get compact output by default; interactive terminals see live streamed command output. Force modes with --verbose (live) or --quiet (compact); they are mutually exclusive, and --format json is always compact. Full combined output of every command is stored per run under ~/.cache/grace/run-commands/<project>/runs/<run>/ (respecting XDG_CACHE_HOME) with a machine-readable meta.json; failing commands print a bounded output tail plus the absolute log path. meta.json records the VCS identity the run executed against (head, branch, dirty, all null outside a git repository) plus the writing pid; it is written at run start with status running and rewritten on completion, and a running record whose process is gone is reclassified as killed on a later run. Pruning keeps the newest passing run of every change indefinitely, so the evidence an archived change cites stays on disk; the retention count applies only to non-passing runs — failed, timed out, interrupted, superseded by a newer pass of the same change, unbound to a change, or missing a readable meta.json. The count defaults to 10, is set project-wide by runLogRetention in .grace-lint.json, and is overridden per run by --keepRuns N. --keepRuns 0 keeps no non-passing runs at all, which deletes the current run as soon as it fails and leaves its printed log path dangling. Interrupted runs (SIGINT/SIGTERM) kill the whole command process group, record interrupted status in meta.json, and exit 130.</command_run_contract>
Show full SKILL.md (120 more words)Show less
<lifecycle_command_contract>current evaluates active approved baselines and is not end-state evidence. Keep MustPassCommand entries as leaf project checks; do not nest grace lint, grace status, or another GRACE lifecycle command inside plan assertions. Run selected target/final lint externally.</lifecycle_command_contract>
<failure_contract>
Lint, status, and navigation commands validate before returning records. JSON argument/runtime failures are one { "schemaVersion": "1.0.0", "ok": false, "error": { ... } } object on stdout. Text failures are one concise actionable line with a nonzero exit code and no stack trace.
</failure_contract>
<runtime_contract>
TypeScript/JavaScript analysis is bundled. Python and Dart governed files require their runtimes on PATH; missing runtimes fail closed with actionable analysis.runtime-missing diagnostics instead of silently dropping parity checks.
</runtime_contract>
<migration_boundary>GRACE 4 commands do not dual-validate legacy GRACE 3 docs. Use grace-migrate.</migration_boundary>
</skill>
© osovv, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/grace/grace-cli of osovv/grace-marketplace.
Open the folder on GitHubat commit 70f5ec4
Compare with similar skills
Grace CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Grace CLI this skillosovv/grace-marketplace | 252 | — | ~1k | Automated safety check: Pass | MIT | |
| Install Anti-Slop Oxlint Rulesdmmulroy/anti-slop | 5.3k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Summarise Ecosystem Resultsastral-sh/ruff | 50k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Minimizing Ty Ecosystem Changesastral-sh/ruff | 50k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Babysit PR To Pass CIsgl-project/sglang | 37k | 2 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| Rust Best Practicesfarm-fe/farm | 5.6k | 3 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Summarise Ecosystem Results
astral-sh/ruff
A skill your agent uses when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem…
- Official
Minimizing Ty Ecosystem Changes
astral-sh/ruff
A skill your agent uses when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypyprimer difference"…
Babysit PR To Pass CI
sgl-project/sglang
Start and persistently pursue a goal to babysit an SGLang pull request until selected GitHub Actions workflows pass on the latest PR head.
Rust Best Practices
farm-fe/farm
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.
Go Pedantry
chromedp/chromedp
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
More from osovv/grace-marketplace
All 10 skills in this repoGrace Migrate
osovv/grace-marketplace
Agent-applied GRACE 3 to GRACE 4 migration workflow. An agent skill from osovv/grace-marketplace.
Grace Plan
osovv/grace-marketplace
Read an approved GRACE 4 GraceChangeSpec and optional design context, then create a GraceChangePlan with assertions, scopes, tasks, and verification gates.
Grace Spec
osovv/grace-marketplace
Interview the user and create an approved GRACE 4 GraceChangeSpec plus optional design-context.xml inside .grace/changes/active/C-/.
Grace Init
osovv/grace-marketplace
Bootstrap a Full GRACE 4 project by creating the canonical .grace context, graph, verification, and changes skeleton.
Grace Execute
osovv/grace-marketplace
Execute an approved GRACE 4 GraceChangePlan in sequential or parallel-safe mode with recovery-aware preflight and centralized durable apply.
Grace Explainer
osovv/grace-marketplace
Explain GRACE 4 methodology, .grace artifacts, semantic anchors, change lifecycle, verification, and migration boundaries.
Related
Categories
Questions about Grace CLI
What does Grace CLI do?
Operate the GRACE 4 CLI for .grace linting, status, module navigation, verification navigation, and file-local semantic markup. Grace CLI is an agent skill from osovv/grace-marketplace.grace linting, status, module navigation, verification navigation, and file-local semantic markup.
When should I use Grace CLI?
Grace CLI fits situations like: tasks that involve Linting and formatting.
How do I install Grace CLI in Claude Code?
Run `npx skills add osovv/grace-marketplace --skill grace-cli -a claude-code`. Or copy the skill folder (skills/grace/grace-cli in osovv/grace-marketplace) into .claude/skills/grace-cli in your project. Claude Code loads it when a task matches its description.
How do I install Grace CLI in Codex?
Run `npx skills add osovv/grace-marketplace --skill grace-cli -a codex`. Or copy the skill folder (skills/grace/grace-cli in osovv/grace-marketplace) into .agents/skills/grace-cli in your project. Codex loads it when a task matches its description.
Can I use Grace CLI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add osovv/grace-marketplace --skill grace-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grace-cli, .gemini/skills/grace-cli, .github/skills/grace-cli and .opencode/skills/grace-cli in your project.
What does Grace CLI need to run?
Going by SKILL.md and its folder, Grace CLI needs the command-line tools its instructions call (bun). Our summary lists: Python 3.
Does Grace CLI access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Grace CLI safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Grace CLI use?
Grace CLI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Grace CLI use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Grace CLI?
Skills that share tags, products or a category with Grace CLI: Install Anti-Slop Oxlint Rules (dmmulroy/anti-slop, 5.3k stars), Summarise Ecosystem Results (astral-sh/ruff, 50k stars), Minimizing Ty Ecosystem Changes (astral-sh/ruff, 50k stars) and Babysit PR To Pass CI (sgl-project/sglang, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grace CLI?
osovv (a GitHub user) maintains it in osovv/grace-marketplace, which has 252 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 24, 2026.
Source: osovv/grace-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.