Borrowing it
Nothing to install: this file belongs to edochi/mdvs. 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/edochi/mdvs/main/.claude/skills/issue/SKILL.mdgit clone --depth 1 https://github.com/edochi/mdvsWrote 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/edochi/mdvs/issue)<a href="https://agentmods.dev/skills/edochi/mdvs/issue"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/issue/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/edochi/mdvs/issue"><img src="https://agentmods.dev/badge/skills/edochi/mdvs/issue.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.00024 | $0.00717 |
| Opus 5.5 | $0.00010 | $0.00287 |
| Sonnet 5.5 | $0.00005 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
issue 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issues + Project
Issues live in edochi/mdvs. The project board is at
https://github.com/users/edochi/projects/2 (number 2, ID
PVT_kwHOA2NvhM4BQ-9Z).
Issue structure
Every issue follows this template:
# Summary
One line or short paragraph.
# Changes
- Bullet list of concrete changes
# Description
Free-form, as detailed as needed.
## Sub-header
...
# Files
- `src/cmd/build.rs` — description
The Description section is optional but can be arbitrarily detailed with sub-headers.
Metadata split
On the issue (repo-level):
- Title
- Body (template above)
- Labels — type only:
feat,fix,refactor,docs,test,chore,ci,perf,style - State: open / closed
On the project (board-level):
- Status: Todo / In Progress / Done (syncs with issue state automatically)
- Priority: high / medium / low
Creating an issue
gh issue create --repo edochi/mdvs \
--title "<title>" \
--label "<type>" \
--body "$(cat <<'EOF'
# Summary
...
# Changes
- ...
# Files
- ...
EOF
)"
The issue is auto-added to the project via the project's auto-add workflow.
Setting priority on the project
After creating an issue, set its priority on the project board:
- Get the project item ID:
gh project item-list 2 --owner edochi --format json --jq '.items[] | select(.content.number == <ISSUE_NUMBER>) | .id'
- Set priority:
gh project item-edit --project-id "PVT_kwHOA2NvhM4BQ-9Z" \
--id "<ITEM_ID>" \
--field-id "PVTSSF_lAHOA2NvhM4BQ-9Zzg-8kwo" \
--single-select-option-id "<OPTION_ID>"
Priority option IDs:
- high:
20a900f0 - medium:
4fedbaba - low:
20cdb34f
Dependencies
Managed through GitHub issue relationships, not in the issue body. Use sub-issues or "tracked by" links in the project.
Branch naming
Branches reference the issue number:
<issue-number>-<short-description>
Examples: 1-cargo-dist, 5-enum-constraints, 12-mdbook-site
Querying issues
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 · 135 lines · 24 tokens per session scan A bced7e0fba43
issue is a skill published in the GitHub repository edochi/mdvs (27 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 717 once invoked, about $0.0001 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-05.
Other skills, from other repositories
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.