Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentnpx agentmods add skills/matrixfounder/agentic-development/known-issues-formatWrote 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/matrixfounder/agentic-development/known-issues-format)<a href="https://agentmods.dev/skills/matrixfounder/agentic-development/known-issues-format"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/known-issues-format/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/matrixfounder/agentic-development/known-issues-format"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/known-issues-format.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 80 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00103 | $0.03727 |
| Opus 5.5 | $0.00041 | $0.01491 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 103 tokens to every session and 3,727 once invoked, about $0.0004 per session on Opus 5.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
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.
02-user-stories
Produces or refines ordered User Stories from an Epic, Product Brief, PRD, or bounded request. Use when the user wants to slice, write, assess, order, or persist Stories. Not for Epics or implementation.
07-epic
Produces or refines an outcome-based Epic for a product backlog. Use when the user wants to frame, review, resume, or persist an Epic. Not for Product Briefs, User Stories, or implementation.
09-defect
Produces or refines a backlog Defect from an observed product mismatch. Use when the user wants to report, assess, link, order, transition, or verify a defect. Not for incident response, debugging, or implementation.
01-ticket-info
Retrieve and display a ticket from the configured ticketing tool. Use when the user wants to see, show, or look up a ticket's details. Not for creating a ticket, or commenting on, transitioning, or reassigning one.
nw-deliver
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation.