Borrowing it
Nothing to install: this file belongs to Pratiyush/llm-wiki. 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/Pratiyush/llm-wiki/master/.claude/skills/project-maintainer/SKILL.mdgit clone --depth 1 https://github.com/Pratiyush/llm-wikiWrote 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/pratiyush/llm-wiki/project-maintainer)<a href="https://agentmods.dev/skills/pratiyush/llm-wiki/project-maintainer"><img src="https://agentmods.dev/badge/skills/pratiyush/llm-wiki/project-maintainer.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00099 | $0.01479 |
| Opus 5 | $0.00049 | $0.00740 |
| Sonnet 5 | $0.00020 | $0.00296 |
| Haiku 4.5 | $0.00010 | $0.00148 |
Grade A, and why
project-maintainer 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 8d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-maintainer
What this skill does
The Maintainer owns the full Open Source Framework v4.1 pipeline on a project. Given the current repo state, it:
- Audits phase gates — are we in the right phase? Are the deliverables for the current phase complete?
- Reconciles task tracking — keeps
tasks.md,_progress.md, and GitHub issues in sync (the framework's "dual-tracking" rule). - Runs stale checks — flags content, links, and claims older than the stale threshold.
- Triggers CI — re-runs the privacy grep, performance budget check, and link checker.
- Reports next action — tells the user exactly what to do next and why.
It works for any project that follows the framework — not just llmwiki.
When to invoke
- "Maintain the project" / "maintenance check" / "do a health check"
- "Update progress" / "reconcile tasks" / "sync tasks"
- "Check phase gate" / "can I move to the next phase"
- "Lint the wiki" / "check for stale entries"
- "Monthly verify" / "quarterly review"
- Any time the user is unsure what to work on next
Framework phase awareness
| Phase | The Maintainer's job in this phase |
|---|---|
| 0 Capture | Verify idea-brief.md exists and names target users + the 10x mechanism |
| 1 Validate | Verify scorecard /25 is in _progress.md and ≥20 |
| 1.25 Research | Verify .temp/ has at least 10 cloned reference repos and docs/research.md exists with a gap matrix |
| 1.5 Steering | Verify _progress.md has "Key Decisions" table filled in |
| 1.75 Agent Survey | For agent-native tools — verify adapter compatibility matrix exists |
| 2 Brand | Verify README.md, LICENSE, and badges are in place |
| 3 Structure | Verify folder layout matches docs/architecture.md |
| 4 Content | Track which M items in docs/roadmap.md are ✅ vs [ ] |
| 5 Contribution | Verify CONTRIBUTING.md, PR template, issue templates, CI workflow |
| 5.25 Adapter Flow | For agent-native tools — verify adapter contract doc + at least one community contribution example |
| 5.5 Pre-Launch QA | Run the full QA checklist from docs/framework.md |
| 6 Launch | Verify git tag + GitHub Release + social posts drafted |
| 6.5 Self-Demo | Verify GitHub Pages workflow triggered and live URL returns 200 |
| 7 Grow | Track stars / forks / downloads week-over-week |
| 7.5 Living Knowledge | Verify public wiki is updating on release |
| 8 Maintain | Run monthly verification, merge PRs, update stale entries |
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.
- 8d ago First seen · 114 lines · 99 tokens per session scan A b51d1089c95f
project-maintainer is a skill published in the GitHub repository Pratiyush/llm-wiki (385 stars, last pushed 2mo ago), licensed MIT. It adds 99 tokens to every session and 1,479 once invoked, about $0.0005 per session on Opus 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-30.
Other skills, from other repositories
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.