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 YourTechBud/coding-harness-config --skill analyze-current-stategit clone --depth 1 https://github.com/YourTechBud/coding-harness-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/yourtechbud/coding-harness-config/analyze-current-state)<a href="https://agentmods.dev/skills/yourtechbud/coding-harness-config/analyze-current-state"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/analyze-current-state/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/yourtechbud/coding-harness-config/analyze-current-state"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/analyze-current-state.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.00038 | $0.00611 |
| Opus 5.5 | $0.00015 | $0.00244 |
| Sonnet 5.5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
analyze-current-state 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 2mo 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 — 35 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Current State
Create a decision-enabling account of how the existing system works within the scope of the supplied story. Treat the story as immutable product scope, use the repository as evidence, and limit changes to the requested Markdown artifact. Write the complete analysis there so downstream architecture and program design can proceed without repeating broad discovery.
Artifact Contract
Cover the following knowledge in the form that best fits the system and story:
- Analysis basis and boundary: Identify the story, the relevant system boundary, the code revision when readily available, relevant working-tree divergence, and material evidence sources beyond code.
- Current-system model: Explain the relevant responsibilities, boundaries, relationships, and consequential runtime, data, and state flows from initiation to observable effect. Include variants such as asynchronous execution, failure behavior, configuration, persistence, or external integration when they affect the story.
- Story-to-system trace: Account for every acceptance criterion, constraint, and distinct promised outcome. Connect each one to current behavior or an explicit gap, its entry point, participating components, state, contracts, tests, supporting evidence, and existing mismatches that downstream design must address. Keep this trace easy to find and audit.
- Consequential contracts, constraints, and change surface: Capture the story-relevant APIs, schemas, persisted representations, configuration, invariants, compatibility obligations, external boundaries, extension seams, coupling, and dependencies that shape future design. Describe where change pressure exists without choosing the change.
- Material uncertainty and conflicting evidence: State relevant facts the repository cannot establish, meaningful inferences, and discrepancies among code, tests, documentation, configuration, or observed behavior. Give the strongest account the evidence supports.
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.
- 2mo ago First seen · 35 lines · 38 tokens per session scan A dba53b385157
analyze-current-state is a skill published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 611 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-08-31.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.