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.
git clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/commands/yeaight7/agent-powerups/semantic-change-check)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/semantic-change-check"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/semantic-change-check.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.00015 | $0.00254 |
| Opus 5 | $0.00008 | $0.00127 |
| Sonnet 5 | $0.00003 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
semantic-change-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 8d 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
Semantic Change Check Command
CRITICAL BEHAVIORAL RULES
- Protect Business Trust: The semantic layer is the source of truth for the business. A silent change to a metric definition is worse than a broken pipeline.
- Review YML Only: Focus your analysis on the
.ymlfiles defining metrics, semantic models, and dimensions.
Execution Steps
- Read the changed semantic layer files.
- Identify modifications to
metrics:. If a calculation (expr) or aggregation type changed, flag it as a breaking change. - Identify modifications to
semantic_models:. Ensure primary keys (entities) and dimensions are correctly mapped to the underlying SQL model. - Check for removed metrics or dimensions. Flag these as critical breaking changes for downstream consumers.
- Provide a concise report:
- Blast Radius: (What dashboards/consumers are affected?)
- Breaking Changes: (List of broken metrics/dimensions)
- Recommendations: (e.g., "Version the metric instead of modifying it in place.")
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.
- 8d ago First seen · 23 lines · 15 tokens per session scan A 9cba3ca522a9
semantic-change-check is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 254 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 commands, from other repositories
create-migration
Create a new database migration file with up and down functions.
analyze-query
Analyze SQL query execution plan and provide optimization recommendations.
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
audit-accessibility
Audit web page or component for WCAG accessibility compliance.
t800-update
A command for updating the T-800 agent system from its GitHub repository. GitHub is a service for storing and versioning code.
validate-pipeline
Validate data pipeline configuration and data quality rules.