Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ValorVie/custom-skillsnpx agentmods add skills/valorvie/custom-skills/methodology-systemWrote 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/valorvie/custom-skills/methodology-system)<a href="https://agentmods.dev/skills/valorvie/custom-skills/methodology-system"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/methodology-system/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/valorvie/custom-skills/methodology-system"><img src="https://agentmods.dev/badge/skills/valorvie/custom-skills/methodology-system.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.00061 | $0.01733 |
| Opus 5 | $0.00030 | $0.00866 |
| Sonnet 5 | $0.00012 | $0.00347 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
methodology-system 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 6d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!WARNING] Experimental Feature / 實驗性功能
This feature is under active development and may change significantly in v4.0. 此功能正在積極開發中，可能在 v4.0 中有重大變更。
Methodology System Skill
Language: English | 繁體中文
Version: 2.0.0 Last Updated: 2026-01-25
Overview
The Methodology System provides a unified framework for managing development methodologies in projects that adopt Universal Development Standards.
Two Independent Systems
┌────────────────────────────────────────────────────────────────────────────┐
│ Two Independent Methodology Systems │
├────────────────────────────────────────────────────────────────────────────┤
│ │
│ System A: SDD (AI-Era Methodology) │
│ ───────────────────────────────────── │
│ /spec → Review → /derive-all → Implementation → Verification │
│ Best for: New projects, AI-assisted development, greenfield features │
│ │
│ System B: Double-Loop TDD (Traditional) │
│ ───────────────────────────────────── │
│ /bdd (Outer Loop) → /tdd (Inner Loop) → Demo │
│ Best for: Legacy systems, manual development, established codebases │
│ │
│ Optional Input: ATDD Workshop │
│ ───────────────────────────────────── │
│ Stakeholder collaboration that feeds into EITHER system │
│ │
└────────────────────────────────────────────────────────────────────────────┘
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 252 lines · 61 tokens per session scan A 2098691aae1b
methodology-system is a skill published in the GitHub repository ValorVie/custom-skills (5 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,733 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
implement
Implement a technical design by decomposing it into dependency-ordered vertical slices, executing each with TDD red-green, reviewing each via an isolated sub-agent, and persisting progress to a state file so work survives session restarts. Use when the user has a tech design (doc or settled conversation) and says…
tdd
A Test-Driven Development guide. TDD means writing a failing test first, adding the smallest implementation that passes it, and then improving the code while keeping the tests passing.
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…
ralphctl-test-driven-development
Execute-phase skill — write the failing test before the code that makes it pass; for bug fixes, this is the reproduction test itself. Use for any logic change, bug fix, or behavioural modification; for the full root-cause triage pipeline around an unexpected failure, see ralphctl-debugging-and-error-recovery.
armada-tdd
Test-driven development for armada workers. Use before writing any implementation. Triggers on: TDD, failing test, test first, write a test.