Claude With Skills is a progressive course that teaches developers to create reusable, portable Agent Skills for Claude Code, from basic SKILL.md files to advanced automation and plugin packaging. It is intended for developers who want repeatable instructions and workflows instead of repeatedly pasting the same guidance. The catalogue contains the course's skills, agents, and instruction.
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 davila7/claude-with-skills --skill fix-issuegit clone --depth 1 https://github.com/davila7/claude-with-skillsWrote 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/davila7/claude-with-skills/fix-issue)<a href="https://agentmods.dev/skills/davila7/claude-with-skills/fix-issue"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/fix-issue/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/davila7/claude-with-skills/fix-issue"><img src="https://agentmods.dev/badge/skills/davila7/claude-with-skills/fix-issue.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00025 | $0.00497 |
| Opus 5 | $0.00013 | $0.00249 |
| Sonnet 5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
fix-issue 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 10d 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.
What it actually says
Fix GitHub issue
Step 1: Read the issue
Run:
gh issue view $ARGUMENTS
If the issue does not exist or the gh CLI is not authenticated, stop and report the error. Do not proceed.
Step 2: Understand the requirements
From the issue output, identify:
- The reported problem or requested feature
- Any reproduction steps or acceptance criteria mentioned in the issue body
- Labels that indicate the type of work (bug, enhancement, documentation, etc.)
- Any linked issues or pull requests that provide additional context
If the issue is unclear or underspecified, state the assumptions you are making before proceeding.
Step 3: Find the relevant code
Search for code related to the issue:
- Use
grep -rto find files referencing the relevant function, component, or error message - Read the most relevant files to understand the current implementation
- Identify where the change should be made and why
Step 4: Implement a minimal fix
Make the smallest change that correctly addresses the issue. Follow the existing code patterns in the affected file:
- Match the style, naming conventions, and error handling patterns already in use
- Do not refactor unrelated code
- Do not add features beyond what the issue describes
Step 5: Write or update tests
If the codebase has tests:
- Add a test that fails before the fix and passes after
- Update any existing tests that are affected by the change
- Run the existing tests to confirm nothing is broken (use the test runner you find in
package.jsonor the nearest test configuration file)
If you cannot determine the test runner, note that and ask the user.
Step 6: Prepare a commit message
Stage the changes and write a commit message in this format:
fix: <short description matching the issue title>
Fixes #$ARGUMENTS
Do not commit automatically. Present the staged diff and the proposed commit message, then wait for the user to confirm or adjust before committing.
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.
- 10d ago First seen · 65 lines · 25 tokens per session scan A 6fb6dcf18214
fix-issue is a skill published in the GitHub repository davila7/claude-with-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 497 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
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.