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 skills add monkilabs/opencastle --skill project-consistencygit clone --depth 1 https://github.com/monkilabs/opencastleWrote 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/monkilabs/opencastle/project-consistency)<a href="https://agentmods.dev/skills/monkilabs/opencastle/project-consistency"><img src="https://agentmods.dev/badge/skills/monkilabs/opencastle/project-consistency.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.1 | $0.00041 | $0.00643 |
| Opus 5 | $0.00020 | $0.00321 |
| Sonnet 5 | $0.00008 | $0.00129 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
project-consistency 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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Consistency
Produce shared artifacts and automated checks before parallel work begins.
Foundation-First Principle
Phase 1 (sequential): foundation-setup creates tokens, Layout, UI library, style guide brief. Phase 2 (parallel): every page task imports from Phase 1 — no new tokens, no duplicated components.
Foundation Artifacts & Page Rules
| Artifact | Path | Page Agent Rules |
|---|---|---|
| Design tokens | src/styles/tokens.css |
Import only. Never introduce new color/font/spacing values. |
| Shared layout | src/components/Layout.tsx / Layout.astro |
Wrap every page. Never recreate. |
| UI components | src/components/ui/ |
Import from library. PascalCase components, camelCase props. |
| Style guide brief | Inline in prompts | Match tone + terminology exactly. Follow heading hierarchy. |
Validation checkpoints:
- Foundation complete:
tokens.csshas all palette/type/spacing vars, Layout renders, UI components compile. - Per-page:
grep -rF 'style={{' src/pages/returns 0 hits (no inline styles). All imports resolve.
Convoy Integration
Include these 5 Foundation References in every page prompt:
1. Design tokens path 2. Layout path 3. UI components path
4. Aesthetic direction 5. Content tone
Prompt templates: see TEMPLATES.md.
Example: src/styles/tokens.css
:root {
/* Palette */
--color-bg: #ffffff;
--color-foreground: #0f172a;
--color-primary: #0ea5e9;
--color-primary-600: #0284c7;
/* Typography */
--font-base: Inter, system-ui, -apple-system, sans-serif;
--text-sm: 0.875rem;
--text-base: 1rem;
/* Spacing */
--space-1: 4px;
--space-2: 8px;
--space-3: 16px;
/* Radius */
--radius-sm: 6px;
--radius-md: 12px;
}
UI components consume these vars only — e.g. bg-[var(--color-primary)], never a literal hex.
Anti-Patterns
| Anti-pattern | Fix |
|---|---|
| Agents pick their own fonts/colors | Foundation creates tokens first |
Copy-pasting Button between pages |
Import from shared library |
Inline style={{ color: '#...' }} |
CSS class with token variable |
| Foundation and page tasks run in parallel | Foundation phase must fully complete first |
What ships with it
1 file 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.
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.
- 3d ago First seen · 81 lines · 41 tokens per session scan A 13b084b13a30
project-consistency is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 643 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-09-03.
Other skills, from other repositories
simplify-skill
Universal, high-intelligence ecosystem-aware code simplification skill. Detects ANY programming language, framework, package manager, and exact version in use. Consults modern documentation via web search and Context7, and orchestrates specialized sub-agents applying strict, universal engineering heuristics.
code-review
Use when code has been written and needs validation before committing, or when the user asks for a code review or security check.
code-review
AI-powered code review for diffs and individual files using LLM analysis.
code-review-github
GitHub PR workflow orchestration for code review — list PRs, post comments, apply labels, and guarded auto-merge.
code-review-standards
Discover and apply organization coding standards from .forge-review/ configuration.
product-architect
Complete product development system with 80 agents and 36 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…