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/ph3on1x/wisci/commitnpx skills add ph3on1x/wisci --skill commitgit clone --depth 1 https://github.com/ph3on1x/wisciWhat 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.00048 | $0.01222 |
| Opus 5 | $0.00024 | $0.00611 |
| Sonnet 5 | $0.00010 | $0.00244 |
| Haiku 4.5 | $0.00005 | $0.00122 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/commit — Context-Enriched Committer
Create git commits that track AI context evolution alongside application changes. When AI-layer files are part of the commit, a Context: section is appended to the commit body — making git log long-term, queryable memory for future sessions and agents.
Current state
!git status
!git --no-pager diff --stat HEAD
Recent commits (style reference):
!git log --oneline -5
If the blocks above show errors or unexpanded variables, run the commands yourself with Bash.
Execution Flow
-
Parse arguments. If
$ARGUMENTSstarts with the standalone wordpush(case-insensitive): enable push-after-commit, use the remainder as the commit message (may be empty). -
Check for committable changes in the state above. Nothing staged, unstaged, or untracked → report "Nothing to commit — working tree clean." and stop. Run
git --no-pager diff HEADfor the full diff when the stat summary is not enough to write an accurate message. -
Classify every changed and untracked file:
- Application code — stage normally
- AI context files (paths below) — stage normally; flag for the Context section
- Sensitive files (
.env,*.key,*.pem,credentials.*,*secret*) — do not stage; warn the user - Unrelated concerns — if changes span multiple unrelated concerns and
$ARGUMENTSgives no hint, ask before bundling
-
Stage files individually (
git add <file>). Nevergit add -Aorgit add .. -
Detect AI context changes. Check
git --no-pager diff --cached --name-onlyagainst the AI Context Paths below. -
Draft the message.
$ARGUMENTSprovided: use it; prepend a conventional prefix (feat:,fix:,refactor:,docs:,test:,chore:) if missing, inferred from the changes.- Empty: auto-generate from the staged diff — focus on why, not what.
-
Append the Context section when AI-layer files are staged (omit entirely otherwise):
Context: - <create|update|remove|rename> <path> — <what changed>
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 First seen · 114 lines · 48 tokens per session scan A 73e8786a3cbc
commit is a skill published in the GitHub repository ph3on1x/wisci (1 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,222 once invoked, about $0.0002 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 skills, from other repositories
contorium-workspace-memory
Use Contorium workspace memory layers (focus, session events, Git, export) when resuming AI work or avoiding repeated project explanation.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent…
docs-impact-architect
Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume /…
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…