Borrowing it
Nothing to install: this file belongs to fqmyysjjd/agent-feed. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fqmyysjjd/agent-feed/main/.agents/skills/project-fix/SKILL.mdgit clone --depth 1 https://github.com/fqmyysjjd/agent-feedWrote 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/fqmyysjjd/agent-feed/project-fix)<a href="https://agentmods.dev/skills/fqmyysjjd/agent-feed/project-fix"><img src="https://agentmods.dev/badge/skills/fqmyysjjd/agent-feed/project-fix.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.1 | $0.00028 | $0.00306 |
| Opus 5 | $0.00014 | $0.00153 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
project-fix 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 6d 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
Project Fix Skill
Required Use
Use this skill for bug fixes, review finding fixes, regression fixes, failed test fixes, merge conflict aftermath, contract drift, or behavior inconsistencies.
Required Reading
.agents/rules/outcome-boundary.md.agents/skills/project-architecture/SKILL.md.agents/skills/engineering-planning/SKILL.md.agents/skills/project-development/SKILL.md.agents/rules/review-gates.md.agents/rules/testing-gates.md.agents/domain/contracts.md
Workflow
- Recover the current task result boundary.
- Use
.agents/skills/engineering-planning/SKILL.mdto decide owner, reuse, placement, write set, boundaries, and verification before editing. - Intake symptom, expected behavior, current behavior, changed files, and affected phase.
- Reproduce or trace the issue.
- Locate the root cause and owner module.
- Apply the smallest fix that preserves boundaries and source-of-truth ownership.
- Add or update tests that would fail before the fix and pass after it when practical.
- Run relevant verification.
- Stop when the declared fix boundary is satisfied.
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.
- 6d ago First seen · 35 lines · 28 tokens per session scan A ca64bb2348ce
project-fix is a skill published in the GitHub repository fqmyysjjd/agent-feed (4 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 306 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-31.
Other skills, from other repositories
bug-capture
Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug"…
dxkit-flow
Configure, diagnose, and repair the dxkit UI→API integration gate — set up flow gating, explain the flow-contract diagnosis, fix a net-new broken integration a guardrail flagged, and run the cross-repo handshake. Use when the user says "set up the flow gate", "why is this call unresolved", "the guardrail says I broke…
incident-triage-harness
Production-style incident triage workflow for logs, metrics, code, safe mitigations, and M3 multimodal visual evidence (screenshots, screen recordings). Use when debugging alerts, regressions, outages, or suspicious runtime behavior.
bughunter
When the user wants to find bugs, test edge cases, stress-test code, or perform adversarial analysis of their codebase. Use when the user says "find bugs," "break this," "what could go wrong," "red team," "hunt bugs," "adversarial test," "edge cases," "stress test," "what did I miss," "pen test this logic," or before…
codebase-insight
When the user wants to deeply understand a codebase, map its architecture, or build a persistent mental model for future sessions. Use when the user says "explain this codebase," "map the architecture," "codebase insight," "understand this repo," "what does this project do," "how does this work," "analyze the…
stuck-recovery
When you or the user are going in circles, stuck on a problem, or repeating failed approaches. Use when the user says "I'm stuck," "this isn't working," "we keep going in circles," "try something different," "nothing works," "help," or when you detect that you've attempted the same category of solution 2+ times…