Borrowing it
Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. 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/zarfld/presonus-studiolive-mcp/master/.github/Skills/github-housekeeping/SKILL.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcpWrote 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/zarfld/presonus-studiolive-mcp/github-housekeeping)<a href="https://agentmods.dev/skills/zarfld/presonus-studiolive-mcp/github-housekeeping"><img src="https://agentmods.dev/badge/skills/zarfld/presonus-studiolive-mcp/github-housekeeping.svg" alt="Measured on agentmods" 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.00000 | $0.00781 |
| Opus 5 | $0.00000 | $0.00391 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
github-housekeeping 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 7d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Housekeeping
Purpose
Use this skill to keep the issue tracker, labels, milestones, and project state aligned with the actual repository state.
The goal is to make the repo understandable to both humans and agents. Open issues should represent real remaining work, not completed history.
Applies to
- GitHub issues
- labels
- milestones
- issue checklists
- release blockers
- completed-but-open issues
- stale TODO tracking
- HIL work queues
Recommended labels
Use a controlled label set.
Type
type:bug
type:feature
type:stub
type:docs
type:refactor
type:test
type:hil-probe
Area
area:routing
area:avb
area:fat-channel
area:write-tools
area:mcp-server
area:adapter
area:domain
area:ci
area:docs
Status
status:planned
status:in-progress
status:implemented-unverified
status:needs-probe
status:blocked
status:observed
status:done
Priority
priority:p0
priority:p1
priority:p2
priority:p3
Required workflow
- List open issues.
- Identify issues that appear completed.
- Identify issues whose title/body overstates completion.
- Identify issues missing acceptance criteria.
- Identify issues missing labels.
- Link each issue to the relevant skill:
- stubs →
stub-placeholder-elimination - routing →
routing-reverse-engineering - HIL →
hil-probe-design - writes →
mcp-write-safety-gate - Fat Channel →
fat-channel-calibration - claims/release →
release-readiness-audit
- stubs →
- Close completed issues only if evidence is linked.
- Convert broad issues into smaller actionable issues if needed.
Required issue template
Each active issue should contain:
## Problem
What is unfinished or wrong?
## Scope
Files/tools/features affected.
## Required skill
Which agent skill should be used?
## Acceptance criteria
- [ ] ...
- [ ] ...
## Evidence required
Unit test / HIL probe / fixture / docs update.
## Capability impact
Which capability matrix entries change?
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.
- 7d ago First seen · 176 lines · 0 tokens per session scan A db46170ff8e0
github-housekeeping is a skill published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 781 tokens. 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.