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 agentmods add skills/benoror/obsidianos_work/commitnpx skills add benoror/obsidianos_work --skill commitgit clone --depth 1 https://github.com/benoror/obsidianos_workWhat 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 | $0.00027 | $0.01355 |
| Opus 5 | $0.00014 | $0.00678 |
| Sonnet 5 | $0.00005 | $0.00271 |
| Haiku 4.5 | $0.00003 | $0.00136 |
Grade A, and why
commit 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit
Usage
| Command | What it does |
|---|---|
/commit |
Commit staged files; if none staged, infer related changes |
/commit <file> |
Scope to a specific file's changes |
/commit <folder>/ |
Scope to a folder's changes |
/commit <description> |
Infer scope from free-text intent |
/commit <scope> <description> |
Scope + explicit intent |
/commit amend |
Amend the last commit (re-use message) |
/commit amend <scope/description> |
Amend with additional scope or new message |
| (sequence mode) | Deferred — sub-skills skip, caller commits once at the end |
Argument Parsing
Parse the raw argument string into scope, intent, and flags:
- Amend flag: If the first word is
amend, set amend mode and strip it. The remainder is parsed normally. - Scope (file or folder): Any token that matches a real path in the repo (file or directory) — whether provided via
@-reference or plain text. Multiple scopes are allowed. - Intent (free-text description): Whatever remains after extracting scopes. Used to guide the commit message.
- Nothing: No arguments at all — default mode.
Examples:
| Input | Scope | Intent | Amend |
|---|---|---|---|
| (empty) | — | — | no |
Meetings/Engineering/ |
Meetings/Engineering/ |
— | no |
.gitignore |
.gitignore |
— | no |
my awesome refactor |
— | my awesome refactor |
no |
Meetings/ wrap up notes |
Meetings/ |
wrap up notes |
no |
amend |
— | — | yes |
amend .obsidian/ |
.obsidian/ |
— | yes |
amend fixed typo |
— | fixed typo |
yes |
Workflow
1. Gather state
Run in parallel:
git diff --staged --stat— staged changesgit diff --stat— unstaged changesgit status --short— untracked filesgit log --oneline -5— recent commits (for style and amend safety)
2. Determine file set
Resolve which files will be committed, based on parsed arguments:
| Scenario | File set |
|---|---|
| Scope provided | Only changed/untracked files under the given path(s). Ignore everything else. |
| Intent provided, no scope | Analyze all changed files; select only those whose diffs relate to the described intent. Present the selection for confirmation. |
| No args + staged files exist | Use exactly what's staged. Do NOT add unstaged files — the user intentionally staged those. |
| No args + nothing staged | Analyze all changed/untracked files. Group related changes and propose a sensible set. Ask for confirmation. |
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.
- 2d ago First seen · 129 lines · 27 tokens per session scan A e96e99f19497
commit is a skill published in the GitHub repository benoror/obsidianos_work (166 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,355 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.
Other skills, from other repositories
plannotator-compound
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.
release-plannotator
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging…
plannotator
Reference for using the Plannotator CLI: plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, and exporting or sharing Guided Reviews. Invoke when asked to use Plannotator for anything not covered by a more specific…
pierre-guard
Guard against breaking the @pierre/diffs integration in Plannotator's code review UI. Use this skill whenever modifying DiffViewer.tsx, upgrading the @pierre/diffs package, changing unsafeCSS injection, adding new props to FileDiff, or touching shadow DOM selectors or CSS variables that cross into Pierre's shadow…
update-deps
Audit and update npm/Bun dependencies with supply chain integrity checks — verifies maintainers, publish age, tarball diffs, and provenance before bumping. Defers risky packages to /.supply-chain/notes/.
plannotator-visual-explainer
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to…