standards_check

A command that checks the current code changes against Smart Citizen's documented project standards. It reports problems with file locations, line references, and severity levels.

In plain words
What is it for?
Use it to inspect staged and unstaged changes for portable-settings issues, worker-thread progress or settings problems, coverage requirements, and other documented checks.
Why use it?
It helps find standards violations before changes are merged, while leaving the fixes for you to review and approve.

Command for Claude Code

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.

agentmods
npx agentmods add commands/osiris-devworks/smart-citizen/standards_check
Clone the repo
git clone --depth 1 https://github.com/Osiris-DevWorks/smart-citizen

Made for: Claude Code.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 991 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00010 $0.00991
Opus 5 $0.00005 $0.00495
Sonnet 5 $0.00002 $0.00198
Haiku 4.5 $0.00001 $0.00099

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

Security

Grade A, and why

standards_check 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 2d 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.

.claude/commands/standards_check.md · 63 lines

How it starts

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

/standards_check

Audit the working-tree diff (staged + unstaged) against the project's documented standards. Report findings with file:line references and severity. Do not auto-fix without confirmation.

Each check carries a severity:

  • Critical — breaks correctness, threading, or release-mode invariants. Must fix before merge.
  • Major — wrong but won't immediately break. Should fix before merge.
  • Minor — stylistic or "consider" notes. Optional.

Checks

  • Portable mode (Critical): direct QSettings(...) constructor calls outside src/utils/settings.py and src/utils/json_settings.py break portable mode silently. Must use AppSettings helpers.
  • Worker progress (Critical): QProgressBar.setValue(...) invoked from inside a QThread worker — must route through ProgressSink (src/utils/progress_sink.py).
  • Worker settings access (Critical): workers in src/gui/workers.py that read QSettings/JsonSettings directly. Settings must be pre-fetched on the main thread and handed to the worker via __init__.
  • DataForge coverage (Critical): new read paths in scripts/generate_enhancements_ini.py without matching entries in DATAFORGE_KEEP_SUBPATHS (src/utils/pak_extractor.py) AND CATEGORY_SUBTREES (src/utils/dataforge_diff.py). Both lists must agree on coverage.
  • Row→entry lookup (Critical): any self.entries[row] indexing or equivalent in src/gui/ — row index ≠ entry index when filtered/sorted. Must use _entry_index_for_row(row).
  • Frontend stamp (Major): any code that writes to the Frontend_PU_Version loc-key without going through _stamp_frontend_version in src/gui/main_window.py — bypasses the no-double-stamp guard.
  • Table column indices (Major): hard-coded literal column numbers in src/gui/ instead of the COL_* constants exported from src/gui/string_table_model.py.
  • base.ini vs global.ini (Major): cached source must be base.ini. New code calling the cached source global.ini is wrong — that name is reserved for the game's file.

Read the full file on GitHub · 63 lines

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. 2d ago First seen · 63 lines · 10 tokens per session scan A 9d8bdad91c63

Subscribe to this mod's changes

standards_check is a command published in the GitHub repository Osiris-DevWorks/smart-citizen (99 stars, last pushed 4d ago), licensed Apache-2.0. It adds 10 tokens to every session and 991 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-30.