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 marconae/speq-skill --skill speq-git-disciplinegit clone --depth 1 https://github.com/marconae/speq-skillWrote 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/marconae/speq-skill/speq-git-discipline)<a href="https://agentmods.dev/skills/marconae/speq-skill/speq-git-discipline"><img src="https://agentmods.dev/badge/skills/marconae/speq-skill/speq-git-discipline.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00600 |
| Opus 5 | $0.00000 | $0.00300 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
speq-git-discipline 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 yesterday.
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
Git Discipline
Git read-only guardrails. User controls all git writes.
Allowed Commands
git status git diff git log git show git branch
Forbidden Commands
add commit push pull fetch
merge rebase cherry-pick
checkout switch restore
reset revert stash tag
No exceptions.
Before Completing Work
Verify expected changes:
git status # Check files changed
git diff # Review actual changes
Tracked vs Gitignored Spec Paths
- Everything under
specs/_plans/<plan-name>/is tracked and committed with the plan directory, never gitignored. This includes the evidence artifacts:open-questions.md(present only while the plan is blocked)review/(plan-review findings,round-<N>.md)review-findings.md(code-review findings)tasks.mdandverification-report.md
- These commits put the evidence trail into history before
/speq-recordarchives the plan (mv specs/_plans/<plan-name> specs/_recorded/NNN-<plan-name>). specs/_recorded/is gitignored by default. This is a default, not an enforced rule: a project can track_recorded/, and the archived plan then lands in history a second time./speq-audit's gitignore-hygiene checks default to this split (_plans/_decisiontracked,_recordedignored). They only offer to align a drifted project, never force it.
Security
Never commit secrets (API keys, passwords, credentials, tokens).
Commit Conventions
Follow the Conventional Commits specification:
<type>[scope]: <description>
[body]
[footer]
| Type | Use |
|---|---|
feat |
New feature (MINOR) |
fix |
Bug fix (PATCH) |
perf |
Performance |
refactor |
Restructure, same behavior |
test |
Tests |
docs |
Documentation |
spec |
Spec changes |
chore |
Maintenance |
Breaking changes: Add ! after type or BREAKING CHANGE: footer → MAJOR version
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.
- yesterday Changed · -2 lines · -64 tokens per session c7faacf05116
- 8d ago First seen · 77 lines · 64 tokens per session scan A 010804c02a57
speq-git-discipline is a skill published in the GitHub repository marconae/speq-skill (50 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 600 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-30.
Other skills, from other repositories
speckit-resolve-pr
Address actionable review feedback on a pull request, push the fixes, and resolve review threads. Reads the PR comments, updates the code, runs project verification, replies to review threads, and reports what changed.
gitops
Git operations wrapper: sync, stage, commit, push. Generates Conventional Commits messages with .scratch artifact references. Use when the user says gitops, commit, push, sync code, or needs version control operations.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.