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 travisjneuman/.claude --skill core-workflowgit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/core-workflow)<a href="https://agentmods.dev/skills/travisjneuman/.claude/core-workflow"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/core-workflow/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/travisjneuman/.claude/core-workflow"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/core-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01917 |
| Opus 5.5 | $0.00021 | $0.00767 |
| Sonnet 5.5 | $0.00010 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
core-workflow 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 24d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Workflow Patterns
Comprehensive development workflow reference. This loads on-demand for detailed patterns.
Quick links to rules: ~/.claude/rules/ for stack-specific and task-type checklists.
Session Protocol
Start Checklist
# 1. Sync first: default branch from origin/HEAD, fetch + prune, fast-forward
git fetch --prune origin && git merge --ff-only "$(git symbolic-ref --short refs/remotes/origin/HEAD)"
# 2. Get context
git log -3
# 3. Check for existing work
ls tasks/*.md 2>/dev/null || echo "No active tasks"
Take today's date from the environment context rather than inferring it.
End Checklist
# 1. Verify by review: re-read the request and the whole diff (no test/type-check ladder)
# 2. Archive completed work
mv tasks/<completed-task>.md .archive/completed-tasks/
# 3. Commit with comprehensive message
git add -A # all pending changes, any session's
git commit # See Git Conventions below
git push # or the configured push runner, when one is defined; never force
Stop any dev server you started: lsof -ti:PORT | xargs kill (or Windows equivalent)
Sizing Work
| Complexity | Workflow |
|---|---|
| Simple fix (<30 min) | Direct execution |
| Single feature (30min-2hr) | Task file + TodoWrite |
| Multi-phase feature (days) | Plan mode, then one task file per phase in tasks/ |
| New project/app | /init-project, then plan mode for the first phase |
Git Conventions
Commit Types
feat | fix | refactor | perf | test | docs | chore
Commit Message Format
type: Short summary (50 chars max)
## What Changed
- File X: Added feature Y
- File Z: Updated config for A
## Why
- User requested feature Y
- Config A needed update
## Verification
- Diff reviewed against the request, callers, and edge cases
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.
- 24d ago Changed · -41 lines 1d69b7b5df2a
- 26d ago Changed · -17 lines · -1 tokens per session 67b92141feb0
- 1mo ago First seen · 351 lines · 53 tokens per session scan A 04bdd32fd32b
core-workflow is a skill published in the GitHub repository travisjneuman/.claude (106 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 1,917 once invoked, about $0.0002 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
ops-standup
Cross-repo morning briefing. Aggregation of recent commits, PRs, CI, blockers and priorities of the day. Trigger when the user wants a standup, an activity summary, or to know what happened.
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode that implements and commits each story one by one. Trigger when the user wants to process a backlog, execute multiple stories, or launch an autonomous mode.
work-commit
Generates clear commit messages following Conventional Commits. Use when the user wants to commit, asks for a commit message, or after completing a modification.
git-workflow
Skill "git-workflow" from halflength-ampleness75/claude-code-recipes, covering git workflow, branch naming, rules, conventional commits and format.
git-commit-generator
Generate Conventional Commits from staged git diff. Analyzes changes and produces commit messages following the Conventional Commits spec (feat, fix, refactor, etc.). Triggers on "generate commit", "write commit message", "conventional commit".
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…