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/jimmypaolini/codebase/triage-submissionnpx skills add JimmyPaolini/codebase --skill triage-submissiongit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/jimmypaolini/codebase/triage-submission)<a href="https://agentmods.dev/skills/jimmypaolini/codebase/triage-submission"><img src="https://agentmods.dev/badge/skills/jimmypaolini/codebase/triage-submission.svg" alt="Measured on agentmods" 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 | $0.00126 | $0.08055 |
| Opus 5 | $0.00063 | $0.04027 |
| Sonnet 5 | $0.00025 | $0.01611 |
| Haiku 4.5 | $0.00013 | $0.00805 |
Grade A, and why
triage-submission 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 — 538 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Submission Failures
Diagnose and fix failures from the Husky pre-commit, commit-msg, and pre-push hooks in this codebase.
When to Use
- A
git commitwas rejected by any hook - A
git pushwas rejected by any hook (branch name validation, pre-push checks) lint-stagedoutput shows failing Nx targets- Errors from tools like ESLint, oxfmt, prettier, oxlint, TypeScript, cspell, markdownlint, yamllint, knip, or vulture appear during a commit or push
commitlintrejects the commit message formatvalidate-branch-namerejects the current branch name on push- Sync checks fail (conventional config, PR template, devcontainer, generator and graph tables, lockfile)
Hook Architecture
pre-commit hook
File: configuration/.husky/pre-commit
NX_PERF_LOGGING=false lint-staged --config configuration/lint-staged.config.ts --continue-on-error
Invoked directly rather than through nx run codebase:lint-staged. That target's own command
still carries NODE_OPTIONS='--import=tsx', which the hook deliberately drops: the flag is
inherited by every command lint-staged runs, and its --import=tsx loader preempts the
transpiler Nx uses for workspace plugins. esbuild emits no design:paramtypes, so the
conformetry plugin's NestJS constructor injection would silently resolve to undefined and the
project graph would fail to build. Node reads the TypeScript config natively instead. The hook
also measures code (nx run codebase:codometer:write) and clears staged notepad files before
running lint-staged.
lint-staged config: configuration/lint-staged.config.ts
Almost every check reaches the staged files through one nx affected run over the
lint-codebase target:
nx affected --target=lint-codebase --configuration=check --parallel=8 --outputStyle=static --files=<path> --files=<path> …
One --files= flag per staged path, never one comma-separated value: Node is
killed by the operating system on a single argument past 1011 bytes, and
lint-staged reports that as Task failed to spawn: undefined with no output.
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 · 538 lines · 126 tokens per session scan A 86614787655a
triage-submission is a skill published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 8,055 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…