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 skills add Kaddo-kdd/kaddo --skill poc-report-writinggit clone --depth 1 https://github.com/Kaddo-kdd/kaddoWrote 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/kaddo-kdd/kaddo/poc-report-writing)<a href="https://agentmods.dev/skills/kaddo-kdd/kaddo/poc-report-writing"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/poc-report-writing/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/kaddo-kdd/kaddo/poc-report-writing"><img src="https://agentmods.dev/badge/skills/kaddo-kdd/kaddo/poc-report-writing.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.00042 | $0.00790 |
| Opus 5.5 | $0.00017 | $0.00316 |
| Sonnet 5.5 | $0.00008 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
poc-report-writing 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 19d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
POC Final Report Writing Skill
Purpose
Turn a supplied deterministic POC report context into a concise, traceable final report.
When to use
After a POC has a canonical conclusion and Core has prepared its deterministic report context.
Rules
- Use only the supplied context; do not scan the repository or infer missing results.
- Treat
poc.mdas canonical for the conclusion. Never contradict it. - Keep facts, measurements, calculations, estimates, and recommendations distinct.
- Never include credential values, tokens, private keys, passwords, or connection strings.
- Use
Not evaluated in this POC.,Not applicable., orNo evidence available.when sources do not support a section. - Return a proposal for human review; Core persists it only after confirmation.
Representation selection
- Use prose for context, interpretation, rationale, findings, and conclusions.
- Use a Markdown table when supplied evidence has comparable rows, such as success criteria and outcomes, resources, experiments, measurements, costs, risks, recommendations, or traceability.
- Use Mermaid only for architecture, topology, or flow relationships explicitly supported by the supplied sources. Prefer it to an ASCII diagram when both can represent the same grounded flow.
- Tables and diagrams are communication tools, not completeness requirements. Do not produce one when the context does not support a useful representation.
- Never invent table rows, diagram nodes or edges, statuses, priorities, metrics, or relationships to make a report look more complete.
- Preserve measured, calculated, estimated, and projected semantics in every representation.
- In Traceability, use repository-relative Markdown links or paths; never emit
file:///URLs or local absolute filesystem paths.
Section representation guide
| Section | Preferred representation when supported by evidence |
|---|---|
| Executive Summary | Snapshot table and short prose |
| Problem and Objective | Prose |
| Hypothesis and Success Criteria | Evaluation matrix |
| Scope, Constraints and Non-goals | Compact bullets or table |
| Technical Approach and Architecture | Mermaid and prose |
| Infrastructure and Project Resources | Table, with optional Mermaid |
| Implementation and Relevant Technical Decisions | Table or concise prose |
| Experiments and Validation | Validation matrix |
| Results and Measurements | Measurement tables |
| Cost and Efficiency Analysis | Comparison table |
| Observability and Operational Findings | Table or prose |
| Findings, Learnings, Limitations and Risks | Structured matrix |
| Conclusion | Status and concise prose |
| Recommendation and Next Steps | Recommendation matrix only when priority is evidenced |
| Traceability and Sources | Relative-link table or list |
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.
- 19d ago First seen · 87 lines · 42 tokens per session scan A 0af6419ad10a
poc-report-writing is a skill published in the GitHub repository Kaddo-kdd/kaddo (67 stars, last pushed 13d ago), licensed MIT. It adds 42 tokens to every session and 790 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…