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.00053 | $0.02309 |
| Opus 5 | $0.00026 | $0.01154 |
| Sonnet 5 | $0.00011 | $0.00462 |
| Haiku 4.5 | $0.00005 | $0.00231 |
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 7d 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 — 351 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 with remote (ALWAYS FIRST)
git fetch origin main && git merge origin/main --no-edit
# or: git fetch origin master && git merge origin/master --no-edit
# 2. Get context
git log -3
# 3. Check for existing work
ls tasks/*.md 2>/dev/null || echo "No active tasks"
CRITICAL: Check <env> section for today's date. NEVER guess dates.
End Checklist
# 1. Verify
npm run test && npm run type-check # or project equivalent
# 2. Archive completed work
mv tasks/<completed-task>.md .archive/completed-tasks/
# 3. Commit with comprehensive message
git add .
git commit # See Git Conventions below
git push origin main
Stop dev server after testing: lsof -ti:PORT | xargs kill (or Windows equivalent)
GSD (Get Shit Done) - Multi-Phase Projects
For complex features spanning days/weeks, use GSD.
When to Use GSD
| Complexity | Use GSD? | Workflow |
|---|---|---|
| Simple fix (<30 min) | No | Direct execution |
| Single feature (30min-2hr) | No | Task file + TodoWrite |
| Multi-phase feature (days) | Yes | GSD workflow |
| New project/app | Yes | GSD from start |
GSD Quick Start
/gsd:new-project # Initialize with brief + config
/gsd:create-roadmap # Create phases and state tracking
/gsd:plan-phase 1 # Create detailed plan for phase
/gsd:execute-plan <path> # Execute the plan
GSD Commands Reference
| Command | Purpose |
|---|---|
/gsd:progress |
Check status, route to next action |
/gsd:resume-work |
Resume from previous session |
/gsd:pause-work |
Create handoff when pausing |
/gsd:plan-phase <n> |
Create detailed phase plan |
/gsd:execute-plan <path> |
Execute a PLAN.md |
/gsd:add-phase <desc> |
Add phase to roadmap |
/gsd:insert-phase <after> <desc> |
Insert urgent work |
/gsd:complete-milestone <ver> |
Archive and tag release |
/gsd:help |
Full command reference |
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.
- 7d ago First seen · 351 lines · 53 tokens per session scan A 04bdd32fd32b
core-workflow is a skill published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 5d ago), licensed MIT. It adds 53 tokens to every session and 2,309 once invoked, about $0.0003 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-workflow
Skill "git-workflow" from halflength-ampleness75/claude-code-recipes, covering git workflow, branch naming, rules, conventional commits and format.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
repo-stats-autoupdate
Keeps README badge + inline counts in sync with the real number of skills, agents, graph nodes/edges, communities, converted pipelines, and test inventory. Runs automatically on every commit via a git pre-commit hook. Use when the README drifts from reality or before publishing a release.
caveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit.…
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.