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 agentmods add skills/matrixfounder/agentic-development/light-modenpx skills add MatrixFounder/Agentic-development --skill light-modegit clone --depth 1 https://github.com/MatrixFounder/Agentic-developmentWhat 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 | $0.00023 | $0.00584 |
| Opus 5 | $0.00012 | $0.00292 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
light-mode 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 2d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Light Mode
Tier: 2 (Load on specific trigger) Purpose: Provide streamlined instructions for trivial, low-risk tasks.
Definition of "Low Risk"
A task qualifies for Light Mode if ALL of the following are true:
- No new files created (except minor config tweaks).
- No database schema changes.
- No API contract changes (endpoints, request/response formats).
- No new dependencies added.
- No modifications to files matching:
auth*,payment*,crypto*,security*. - Estimated implementation time: < 30 minutes.
If ANY condition is false, ESCALATE to standard pipeline.
Instructions by Role
For Analyst
- Mark the TASK title with
[LIGHT]tag. - Keep requirements minimal — focus on "What is broken?" and "What is the expected fix?".
- Skip detailed acceptance criteria if the fix is obvious.
For Developer
- Do not overengineer. Fix the issue directly.
- Do not refactor unrelated code.
- Run tests after every change.
- If you discover complexity (DB migration, API change), STOP and request workflow switch.
For Code Reviewer
- Focus on correctness and tests.
- Skip architectural nitpicks unless they are critical bugs.
- Perform a basic security sanity check:
- No credentials or secrets in code.
- No new dependencies without approval.
- No changes to auth/payment/crypto files.
- If security concerns arise, ESCALATE to
security-audit.
Escalation Protocol
If at any point the task complexity exceeds Light Mode scope:
- Inform the user: "This task requires standard pipeline due to [REASON]."
- Switch workflow: Call
/01-start-featureinstead. - The
[LIGHT]tag should be removed from the TASK.
Safety Rules
The following files are PROHIBITED from Light Mode modifications:
**/auth/**,**/authentication/****/payment/**,**/billing/****/crypto/**,**/encryption/****/security/**.env,*.pem,*.key
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.
- 2d ago First seen · 70 lines · 23 tokens per session scan A e3e27253407c
light-mode is a skill published in the GitHub repository MatrixFounder/Agentic-development (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 23 tokens to every session and 584 once invoked, about $0.0001 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-31.
Other skills, from other repositories
add-tests
Generates tests for existing code. Analyzes the target function, method, or class to identify the happy path, error cases, and edge cases, then writes test cases following the project's testing framework and naming conventions. Invoked when the user asks to add tests, write tests, cover code, or increase coverage.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
company-hiring-intelligence
Reverse-engineer what a company is building by scraping their job postings, careers page, LinkedIn Jobs, and engineering blog using TinyFish web agents. Use whenever a user wants to understand a company's strategic direction from hiring signals, do competitive intelligence, figure out a tech stack from job…
Swift Performance Optimization Skill
Use when investigating measured Swift or Apple-platform regressions in CPU, memory, launch, scrolling, animation hitches, image processing, energy, networking, or concurrency, or when designing performance tests and Instruments experiments. Do not use for speculative micro-optimization, ordinary refactoring, or a…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).