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 MatrixFounder/Agentic-development --skill skill-phase-contextgit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/skill-phase-context)<a href="https://agentmods.dev/skills/matrixfounder/agentic-development/skill-phase-context"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/skill-phase-context/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/matrixfounder/agentic-development/skill-phase-context"><img src="https://agentmods.dev/badge/skills/matrixfounder/agentic-development/skill-phase-context.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.01433 |
| Opus 5.5 | $0.00015 | $0.00573 |
| Sonnet 5.5 | $0.00008 | $0.00287 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
skill-phase-context 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 9d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Context Loading Protocol
This skill defines skill loading tiers to optimize token consumption while preserving automation capabilities.
[!IMPORTANT] Single Source of Truth for Skill Loading Strategy. Reference this skill to understand WHEN to load WHICH skills.
TIER 0: System Foundation — ALWAYS LOADED
[!CAUTION] NEVER lazy-load TIER 0 skills. They enable core automation. These skills MUST be available in EVERY session at bootstrap.
| Skill | Tokens | Why Always Load |
|---|---|---|
core-principles |
~519 | Anti-hallucination rules, Stub-First, Documentation First |
skill-safe-commands |
~927 | Enables automation — the archive script, ls, git, tests auto-run |
artifact-management |
~636 | Archiving protocol, file management, dual state tracking |
| TOTAL | ~2,082 | Non-negotiable system foundation |
TIER 0 Loading Rule
- Load at session bootstrap (via
GEMINI.md/.cursorrules) - These skills are loaded BEFORE any phase begins
- Never remove or defer loading of TIER 0 skills
TIER 1: Phase-Triggered — Load on Phase Entry
These skills are phase-specific and loaded when entering the corresponding phase.
| Phase | Skills to Load | Approx. Tokens |
|---|---|---|
| Analysis | requirements-analysis, skill-task-model, artifact-formalizer (contract only), (skill-archive-task if new task) |
~3,100-4,000 |
| Architecture | architecture-design, artifact-formalizer (contract only), (architecture-format-core OR -extended) |
~2,850-4,200 |
| Planning | planning-decision-tree, skill-planning-format, tdd-stub-first, artifact-formalizer (contract only) |
~2,525 |
| Development | developer-guidelines, documentation-standards |
~1,100 |
| Review | Phase-specific -review-checklist skill |
~300-400 |
| Security | security-audit |
~500 |
| VDD | vdd-adversarial, (adversarial-* per workflow) |
~1,000-2,500 |
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.
- 9d ago Changed c372a6a63e5f
- 13d ago Changed · +14 lines dc896a1e7c47
- 1mo ago First seen · 115 lines · 38 tokens per session scan A 097e0a38e762
skill-phase-context is a skill published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 1,433 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
software-test-creation
Write failing tests for a TDD slice based on acceptance criteria and codebase conventions. Use when the "red" phase of red-green-refactor requires tests that define expected behavior before implementation exists. Discovers codebase test conventions first, writes test files that compile or parse but fail because the…
08-debug
Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
workflow
Perform any development work on the ambient-ui component. Full workflow instructions.
fuzzing-patterns
Use when writing fuzz tests for Solidity contracts. Covers property-based testing, input constraining with vm.assume/vm.bound, stateful vs stateless fuzzing, configuring runs, seed corpus, and interpreting counterexamples.
better-auth-security-best-practices
Configure rate limiting, manage auth secrets, set up CSRF protection, define trusted origins, secure sessions and cookies, encrypt OAuth tokens, track IP addresses, and implement audit logging for Better Auth. Use when users need to secure their auth setup, prevent brute force attacks, or harden a Better Auth…
server-api
Use for Nuxt or Nitro server API routes, defineEventHandler, request validation, or server-side auth data access.