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 NVZver/claude-marketplace --skill revise-constitutiongit clone --depth 1 https://github.com/NVZver/claude-marketplaceWrote 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/nvzver/claude-marketplace/revise-constitution)<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/revise-constitution"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/revise-constitution/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.
<a href="https://agentmods.dev/skills/nvzver/claude-marketplace/revise-constitution"><img src="https://agentmods.dev/badge/skills/nvzver/claude-marketplace/revise-constitution.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.00309 |
| Opus 5 | $0.00012 | $0.00154 |
| Sonnet 5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
revise-constitution 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 11d 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
Trace. On load, print first:
=============== [lsa/skills/revise-constitution/SKILL.md] [lsa] ===============
LSA Revise Constitution
See CORE.md. Edits only the constitution and ${specs_root}/standards/.
Role
Standards steward.
Goal
Make the rules a merged feature taught us permanent — one change at a time.
Inputs
| Input | Source |
|---|---|
Constitution + ${specs_root}/standards/ |
self |
| Latest archived feature | discover |
Steps
- Read the inputs. (→ candidate decisions)
- Keep only permanent rules — coding patterns, test rules, agent rules; drop feature-specific or one-off items. (→ proposals)
- Present each change individually: file · section · current vs proposed · one-line reason; take approval. (→ decisions)
- Apply approved edits in place (show before/after); commit on a
constitution/<desc>branch. (→ updated rules)
Output
Updated constitution / standards on a constitution/<desc> branch.
Constraints
- One change at a time; explicit approval each. Touch only the constitution and
${specs_root}/standards/.
/lsa:revise-constitution — manual invocation.
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.
- 11d ago First seen · 45 lines · 23 tokens per session scan A 62f92eabc7f2
revise-constitution is a skill published in the GitHub repository NVZver/claude-marketplace (1 stars, last pushed 16d ago), licensed MIT. It adds 23 tokens to every session and 309 once invoked, about $0.0001 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 skills, from other repositories
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
refactoring-patterns
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when…
team-review
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after…
roslyn-query
Query .NET/C# codebases using Roslyn AST analysis via dotnet run file. Use for tracing data flow, auditing API usage, finding pattern violations, or ad-hoc codebase queries.
review-responder
Use when receiving feedback on code you implemented, responding to reviewer comments, deciding which review suggestions to implement, or pushing back on incorrect review feedback.
codex
Route a task to OpenAI's Codex CLI (codex exec) instead of doing it yourself. Use this skill ANY time the user names codex or types /codex — even for routine work Claude could handle, because the user is choosing to delegate. The intent: 'ask codex', 'have codex review/refactor this', 'check/validate with codex', 'see…