Borrowing it
Nothing to install: this file belongs to ashishpatill/tell-proof. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ashishpatill/tell-proof/master/.cursor/commands/semantic-commits.mdgit clone --depth 1 https://github.com/ashishpatill/tell-proofWrote 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/ashishpatill/tell-proof/semantic-commits)<a href="https://agentmods.dev/commands/ashishpatill/tell-proof/semantic-commits"><img src="https://agentmods.dev/badge/commands/ashishpatill/tell-proof/semantic-commits/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/commands/ashishpatill/tell-proof/semantic-commits"><img src="https://agentmods.dev/badge/commands/ashishpatill/tell-proof/semantic-commits.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.00000 | $0.00535 |
| Opus 5.5 | $0.00000 | $0.00214 |
| Sonnet 5.5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
semantic-commits 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 1mo 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic commits
Rewrite the current branch's uncommitted (or single squashable) work into as many small conventional commits as possible, then push.
Rules
- Use conventional commit subjects only:
feat|fix|docs|test|chore|ci|refactor|perf|build(scope): … - Never mention Cursor, cloud agents, Copilot, or similar tooling in commit messages or PR text.
- One logical change per commit — prefer more commits over fewer. Good splits:
- schema contracts alone
- one detector or pure function
- one capture/helper module
- one fixture file
- tests for one area
- one script or CI wire-up
- docs/tracker updates last (or per doc file)
- Do not squash unrelated packages into one commit.
- Keep commits buildable when practical; if an intermediate commit must be incomplete, keep follow-ups tight and sequential.
- Prefer
git addof specific paths overgit add -A. - After all commits:
git push -u origin <branch>(force-with-lease only when rewriting already-pushed commits on this feature branch). - Update the open PR description if history was rewritten — still no tooling brand names.
Procedure
- Inspect
git statusandgit diff --statagainst the merge base (masterunless told otherwise). - If work is already one fat commit on the feature branch:
git reset --soft <base>then unstage (git reset HEAD) so files are working-tree changes. - Group files into the smallest coherent commits; commit each with a precise message.
- Run
pnpm test(and schema build / web typecheck if schema or web changed) before the final push when feasible. - Push the branch.
- Reply with the commit list (
git log --oneline <base>..HEAD) and the remote branch tip.
Message style examples
feat(schema): add ScenarioMatrix and ProofMatrixResult contracts
feat(core): detect ResponsiveViewportDrift on viewport collapse
feat(corpus): add marketplace-clutter live-site capture
test(core): golden-assert scenario matrix self-compare
ci: smoke proof matrix on UI pull requests
docs: mark Phase 5 scenario matrix as shipped
chore: ignore proof matrix CI artifact
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.
- 1mo ago First seen · 47 lines · 0 tokens per session scan A d271c0437e41
semantic-commits is a command published in the GitHub repository ashishpatill/tell-proof (2 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 535 tokens. 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
revert
Git-aware undo by logical work unit (track, phase, or task).
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
summarize-changes
Summarize recent changes for standup, PR, or documentation.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.