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/matrixfounder/agentic-development/known-issues-formatnpx skills add MatrixFounder/Agentic-development --skill known-issues-formatgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWhat 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.00103 | $0.03727 |
| Opus 5 | $0.00051 | $0.01863 |
| Sonnet 5 | $0.00021 | $0.00745 |
| Haiku 4.5 | $0.00010 | $0.00373 |
Grade A, and why
known-issues-format 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 2d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thin-Index Ledger Format
Purpose: the single source of truth for the format of this framework's two hand-maintained thin-index ledgers — an index file whose every entry is one pointer line to its own record file:
| Defects | Work-items | |
|---|---|---|
| Index | docs/KNOWN_ISSUES.md |
docs/BACKLOG.md |
| Records | docs/issues/<slug>.md |
docs/backlog/<slug>.md |
| Holds | reproducible wrong behavior | enhancement / polish / signal, no broken contract |
| Read by | Analysis phase (avoid repeating bugs), /heal-issues |
Planning phase, humans ranking work |
| Written by | run-feedback file --as defect |
run-feedback file --as work-item |
artifact-management owns the lifecycle of both (living Global Artifacts, never archived,
create-if-absent) and delegates the format to this skill — mirroring how it delegates
ARCHITECTURE.md structure to architecture-format-core.
On the name. This skill began as the
KNOWN_ISSUES.mdcontract and kept its name when the backlog joined it (four repositories symlink this directory by name). One skill, because the mechanics are one thing said once: two near-identical format contracts are exactly the drift that produced the defect this generalization fixed (run-feedback's two filing paths diverged — the defect path wrote index + record, the work-item path inlined the whole body into the index).
Execution Mode
- Mode: hybrid — a prompt-first format contract, plus one maintenance gate script.
Script Contract
- Command:
python3 scripts/check_contract_sync.py - Purpose: fail if the format contract drifts between this
SKILL.md(the authority) and the seed templates — per registry, it compares the status vocabulary, the rank vocabulary (severity / effort), the record frontmatter key set, and the index-line format. - Outputs / failure semantics: exit
0in sync ·1drift (prints the registry and the diverging field) ·2extraction error. - Idempotent, read-only, no args, no dry-run needed. CI-gateable alongside
System/scripts/validate_skills.py.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 242 lines · 103 tokens per session scan A 822c3ac63ad5
known-issues-format is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 103 tokens to every session and 3,727 once invoked, about $0.0005 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
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…
docs-planner
Identify documentation gaps and prioritize the docs backlog. Use when planning a docs improvement sprint, after signals surface repeated friction, when new SDK features ship without docs, or for periodic health assessment. Also triggers on "plan docs work", "what docs need writing", "prioritize the backlog", "docs…
team-workflow
Design the team's operating rhythm — task management, collaboration rituals, and tooling. Use when the day-to-day cadence needs structure. For a time-boxed sprint, use design-sprint-plan.
design-sprint-plan
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use team-workflow.
nw-buddy-project-reading
How the nWave buddy agent reads a project to answer questions — detection, order of inspection, and citation discipline.
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…