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 synaptiai/synapti-marketplace --skill change-classificationgit clone --depth 1 https://github.com/synaptiai/synapti-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/synaptiai/synapti-marketplace/change-classification)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/change-classification"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/change-classification/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/synaptiai/synapti-marketplace/change-classification"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/change-classification.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.00086 | $0.00902 |
| Opus 5.5 | $0.00034 | $0.00361 |
| Sonnet 5.5 | $0.00017 | $0.00180 |
| Haiku 4.5 | $0.00009 | $0.00090 |
Grade A, and why
change-classification 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 19d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Classification
Contract
Iron law: classify before committing — every changed file gets a classification; unclassified files are not staged. Invoked by /flow:commit (Phase 2 CLASSIFY, cross-check), /flow:start (CODE phase per-task gate, step 8), /flow:address (after fixes), /flow:debug, and /flow:pr (pre-flight). Returns a finding-first table — File | Classification | Signal | Notes — with each file marked in-context, uncertain, out-of-context, or RED FLAG, plus first-touch notes and proposed atomic commit groups. Permitted skips: none. Red-flag files are blocked regardless of context; uncertain or out-of-context files go to the user via a six-field AskUserQuestion escalation before any commit.
Signals
Evaluate in order: red flags, primary, secondary, default → uncertain.
| Category | Signal | Result |
|---|---|---|
| Red flag | .env, .env.<environment> (not .env.example / .env.sample, which are committable templates), credentials*, *secret*, key files |
BLOCK — never commit |
| Red flag | *.lock, package-lock.json, files >1MB, auto-generated |
WARN — verify intentional |
| Primary | In branch diff (git diff --name-only $DEFAULT_BRANCH...HEAD) |
in-context |
| Primary | Path matches issue title/body keywords | in-context |
| Primary | Path referenced in a TaskList task, or same top-level directory as task files | in-context |
| Secondary | Sibling of an in-context file; test companion (foo.rb ↔ foo_test.rb) |
lean in-context |
| Secondary | Config/dotfile/manifest in project root | uncertain |
| Secondary | Unrelated directory, no link to issue or tasks | out-of-context |
Boy Scout cleanup (lint, format, typo, obvious bug) in a file already in the branch diff is the boy-scout subtype of in-context and uses the improve commit type. Weights, thresholds, and commit-type inference: references/classification-signals.md.
First-Touch Detection
A file is "first touch" when git log $DEFAULT_BRANCH..HEAD -- file is empty AND it has >50 lines added. Note it regardless of classification; it gets extra review attention.
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.
- 19d ago Changed f711dec7c2a2
- 1mo ago Changed c012280cfa83
- 1mo ago Changed · -45 lines 8339200e5f40
- 1mo ago First seen · 98 lines · 86 tokens per session scan A 3f22860437b3
change-classification is a skill published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 12d ago), licensed Apache-2.0. It adds 86 tokens to every session and 902 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
loop-close
Closes a slice or a session - adversarial audit of the diff, ledger entry, selective commit, honest report, and the handoff for the next session. Use before considering anything finished.
Implement
Implement one micro spec — one commit, one PR. The micro spec is the complete instruction set; write only the files in its File Operations table, verify against its acceptance criteria, commit.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.