agentmods.dev

grace-lite

grace-lite is a skill for Codex from knopki/agent-skills. It costs 47 tokens per session (2,159 once invoked), scanned A, original, MIT.

A lightweight system for adding structured comments and named code regions that explain how important parts of a project fit together. GRACE means Graph-RAG Anchored Code Engineering, and its markup helps machines navigate code.

In plain words
What is it for?
Use it to initialize or continue GRACE markup, expose public APIs, and review code that uses GRACE markers or purpose comments.
Why use it?
It makes the purpose and boundaries of non-trivial code clearer during setup, maintenance, and review.

Skill for Codex

Written for Codex: agents/openai.yaml present.

not rated 2repo 7d ago A scan 47 tokens original MIT

Good fit Use it to initialize or continue GRACE markup, expose public APIs, and review code that uses GRACE markers or purpose comments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/knopki/agent-skills/grace-lite
View source ↗ knopki/agent-skills
Install

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.

Any agent
npx skills add knopki/agent-skills --skill grace-lite
Clone the repo
git clone --depth 1 https://github.com/knopki/agent-skills

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 grace-lite

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/knopki/agent-skills/grace-lite"><img src="https://agentmods.dev/badge/skills/knopki/agent-skills/grace-lite.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,159 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.00047 $0.02159
Opus 5 $0.00023 $0.01079
Sonnet 5 $0.00009 $0.00432
Haiku 4.5 $0.00005 $0.00216

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

Security

Grade A, and why

grace-lite 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.

The scan reads SKILL.md. This mod also ships 4 executable files (assets/_semantic_template_reference.js, assets/_semantic_template_reference.py, assets/_semantic_template_reference.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/grace-lite/SKILL.md · 229 lines

How it starts

The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Graph-RAG Anchored Code Engineering, lite variant

Overview

GRACE gives a project semantic code markup — region-based contracts and anchors that make code machine-navigable, documentation inside the code.

Also, GRACE methodology offers Log Driven Development as observable contracts.

When to Use

  • The user asks to initialize a project with GRACE markup (activation trigger: "GRACE init") - follow the references/init.md.
  • The user asks to continue / resume adding GRACE markup to a project that was already started - follow the references/init.md.
  • The user asks to review - follow the references/review.md.
  • You are working with code with word PURPOSE in comments.

Markup Reference

Principles

  • Mark up all public and non-trivial code.
  • Expose public API explicitly via language features: __all__ in Python, export in JS/TS, etc.
  • Markup must be proportional to the code's complexity.
  • Python exception: if an entity is annotated by markup, it must always be wrapped in a region (unlike C#, where short top-level entities may use /// <purpose> without #region).
  • For exact comment syntax, refer to the template in _semantic_template_reference.* files in assets directory.

See Common Pitfalls for the corresponding anti-patterns.

Workflow

  1. MODULE_CONTRACT first — always write the module contract before any code. It sets the boundary and purpose of the file.
  2. Public contracts next — define contracts for all public classes, functions, and methods. Create stubs.
  3. Implement — write code inside the contracted regions.

Region Types

MODULE_CONTRACT

File-level contract. Exactly one per file, placed at the very top before all code.

Defines what the module is for and how it relates to the rest of the system.

Fields:

  • PURPOSE — required. The goal of the module: what business/operational need it fulfills.
  • SCOPE — recommended. Functional areas covered by the module and what is explicitly excluded (NOT:).
  • INVARIANTS — recommended. Conditions or states that always hold.
  • USECASES — optional. Scenarios in [Entity]: [Actor] => [Action] => [Goal] format.
  • DEPENDENCIES — optional. Non-trivial dependencies: USES API:, READS:, WRITES:.
  • RATIONALE — optional. Q/A format: why it was implemented this way.
  • KEYWORDS — optional. Comma-separated keywords for grep search.

Read the full file on GitHub · 229 lines

Files

What ships with it

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

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. 9d ago First seen · 229 lines · 47 tokens per session scan A ed4492e2527c

Subscribe to this mod's changes

grace-lite is a skill published in the GitHub repository knopki/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 47 tokens to every session and 2,159 once invoked, about $0.0002 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.

Building agents
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens