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/techygarg/lattice/bug-fixnpx skills add techygarg/lattice --skill bug-fixgit clone --depth 1 https://github.com/techygarg/latticeWrote 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/techygarg/lattice/bug-fix)<a href="https://agentmods.dev/skills/techygarg/lattice/bug-fix"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/bug-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 | $0.00077 | $0.02499 |
| Opus 5 | $0.00039 | $0.01249 |
| Sonnet 5 | $0.00015 | $0.00500 |
| Haiku 4.5 | $0.00008 | $0.00250 |
Grade A, and why
bug-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 4d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix
Required Skills
Load these skills based on bug scope:
framework:knowledge-priming-- Load project context so the diagnosis grounds in the real codebase. (always)framework:context-anchoring-- Find and load the feature's context doc; capture diagnosis and repair decisions in it. (always)framework:learning-harvest-- Load prior operational learnings at session start; harvest new ones at session end. (always)framework:collaborative-judgment-- Surface hypotheses and repair trade-offs as structured options instead of silently assuming. (always)framework:clean-code-- Keep the fix focused, readable, and free of drive-by changes. (always)framework:test-quality-- Regression tests, characterization baseline, assertion quality. (always)framework:architecture-- Layer placement and dependency direction. (conditional: layer placement is in question — Steps 2/4/5)framework:domain-driven-design-- Domain invariants and aggregate behavior. (conditional: domain invariants involved — Steps 2/5)framework:secure-coding-- Trust bounds and sensitive data handling. (conditional: trust boundary crossed — Steps 2/5)
Workflow
Step 1: Establish Bug Context
Start from the failure, not from a proposed fix.
- Gather the observed behavior, the expected behavior, the reproduction path, and any evidence: failing test, error message, stack trace, log excerpt, request payload, recent change.
- Run
framework:learning-harvestLoad behavior. Focus hint: "bug investigation — focus: reliability, quality signals". - Run
framework:context-anchoringDocument Discovery to check for an existing context doc covering the affected feature/module:- Found → Load behavior. Honor every logged decision and constraint as an active commitment while diagnosing. An open investigation of this same bug is already logged in it → confirm with the user whether to resume that investigation or start fresh.
- Not found → Proceed from the bug report and the current code. Do not block diagnosis on a missing context doc.
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.
- 4d ago First seen · 188 lines · 77 tokens per session scan A f489e9320795
bug-fix is a skill published in the GitHub repository techygarg/lattice (183 stars, last pushed 5d ago), licensed MIT. It adds 77 tokens to every session and 2,499 once invoked, about $0.0004 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
xiaoyaoclaw-workspace-initializer
OpenClaw workspace initialization & standardization. Sets up a proper agent home: standard directory structure (projects/tasks/outputs/knowledge/scripts/ memory/tmp) + WORKSPACE.md rules + multi-agent config safety (config.patch, never config.apply) + memory log. Use when an agent enters a new/empty workspace root, or…
learn
Search, install, update, and rate AI agent skills from agentskill.sh (100,000+ skills). Use when the user asks to find skills, install extensions or plugins, discover new capabilities, check what skills are available, or says "how do I do X" when a skill might help. Also handles listing installed skills, checking for…
review-skill
Review and improve AI agent skills (SKILL.md files) against best practices from the Agent Skills specification and Anthropic's authoring guidelines. Scores skills on 10 quality dimensions, identifies specific issues, and rewrites problem areas. Use when creating, editing, auditing, or improving agent skills. Triggers…
building-chatgpt-apps
Guides creation of ChatGPT Apps with interactive widgets using OpenAI Apps SDK and MCP servers. Use when building ChatGPT custom apps with visual UI components, embedded widgets, or rich interactive experiences. Covers widget architecture, MCP server setup with FastMCP, response metadata, and Developer Mode…
memory-systems
Design and implement memory architectures for agent systems. Use when building agents that need to persist state across sessions, maintain entity consistency, or reason over structured knowledge.
scaffolding-openai-agents
Builds AI agents using OpenAI Agents SDK with async/await patterns and multi-agent orchestration. Use when creating tutoring agents, building agent handoffs, implementing tool-calling agents, or orchestrating multiple specialists. Covers Agent class, Runner patterns, function tools, guardrails, and streaming…