Borrowing it
Nothing to install: this file belongs to FilipNowakowicz/nixos-config. 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/FilipNowakowicz/nixos-config/main/.agents/skills/issue-tdd/SKILL.mdgit clone --depth 1 https://github.com/FilipNowakowicz/nixos-configWrote 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/filipnowakowicz/nixos-config/issue-tdd)<a href="https://agentmods.dev/skills/filipnowakowicz/nixos-config/issue-tdd"><img src="https://agentmods.dev/badge/skills/filipnowakowicz/nixos-config/issue-tdd/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/filipnowakowicz/nixos-config/issue-tdd"><img src="https://agentmods.dev/badge/skills/filipnowakowicz/nixos-config/issue-tdd.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.00046 | $0.00648 |
| Opus 5 | $0.00023 | $0.00324 |
| Sonnet 5 | $0.00009 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
issue-tdd 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue TDD
Use this before implementation when an issue or goal is not yet precise enough to build safely. The output is an updated GitHub issue body/comment or a scoped proposal for the user to approve.
Goal
Turn a vague goal into a testable issue:
- problem statement
- desired outcome
- acceptance criteria
- non-goals
- likely touched files or modules
- smallest meaningful validation command
- risks and rollback/deploy concerns
- outcome-changing questions for the user
Workflow
- Read the source item.
- Use
gh issue view <number>for GitHub issues. - For roadmap items, read the linked doc section and nearby context.
- Use
- Inspect only enough repo context to scope the work.
- Use
repo-map-querybefore broad exploration when relevant files are not obvious. - Do not start implementation.
- Use
- Draft the issue in implementation-ready form.
- Use
issue-driven-developmentfor acceptance criteria and proving checks. - Use
nix-verification-loopto choose validation when the touched surface is Nix, shell, docs, host, package, deploy, or profile-test related.
- Use
- Ask only real decisions before implementation.
- Ask about security posture, ownership, deploy risk, product behavior, document ownership, or PR split boundaries.
- Do not ask permission to inspect the repo, run normal validation, or proceed through routine workflow steps.
- Update the GitHub issue when asked, or return a paste-ready issue body/comment.
Decision Gate
If a decision changes the implementation, stop and ask before coding. Use this shape:
I need one decision before this is implementation-ready:
1. <question>
Impact: <what changes depending on the answer>
Ask at most three questions at once. If there are no blocking decisions, say the
issue is ready for issue-driven-development.
Issue Template
## Problem
...
## Desired outcome
...
## Acceptance criteria
- ...
## Non-goals
- ...
## Likely files
- ...
## Validation
- `...`
## Risk / Rollback
- ...
## Decisions
- [ ] ...
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 · 108 lines · 46 tokens per session scan A 84a24a56b5f0
issue-tdd is a skill published in the GitHub repository FilipNowakowicz/nixos-config (5 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 648 once invoked, about $0.0002 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
riglet-creator
Creating effective riglets means writing knowledge (SKILL.md) that agents will rely on. This guide focuses on how to write high-quality documentation for riglets, organized efficiently.
agent-rig-system
A rig is a collection of riglets that provide knowledge and tools for AI agents. Rigs and riglets are packaged as Nix flake outputs, so they can both be used inside the project defining them and by other projects depending on it.
nix-module-system
Practical knowledge about lib.evalModules that's hard to find in official docs.
code-search
Fast, efficient utilities for searching code and browsing file hierarchies.
nixkits-check-updates
A maintenance workflow for checking NixKits software packages against newer upstream releases, applying updates, updating documentation, and recording the work. Nix is a package-management and build system, and a flake is its project configuration file.
write-maintenance-log
A Chinese-language workflow for writing or updating a MAINTENANCE.md software maintenance log. It records software updates and bug fixes, links entries to Git commits, and synchronizes them into five languages.