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/naimkatiman/continuous-improvement/model-forwardnpx skills add naimkatiman/continuous-improvement --skill model-forwardgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/model-forward)<a href="https://agentmods.dev/skills/naimkatiman/continuous-improvement/model-forward"><img src="https://agentmods.dev/badge/skills/naimkatiman/continuous-improvement/model-forward.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 | $0.00062 | $0.00650 |
| Opus 5 | $0.00031 | $0.00325 |
| Sonnet 5 | $0.00012 | $0.00130 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
model-forward 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 3d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model-Forward Skill
The standing mental model for every session: always go with Claude — not against it — until the user says otherwise.
Models improve continuously. Mechanics that skills hand-hold today (planning etiquette, routing, verification reminders) keep merging into the model itself. Betting against that trend produces scaffolding that fights the harness. Betting with it keeps only what stays valuable as models get smarter.
The Two Invariants
Everything in continuous-improvement reduces to two things that survive every model generation:
- Goal-driven execution. Anchor on the highest stated goal — the higher the goal, the better the execution. Tie every change to it, refuse scope creep, stop when it is met. (Laws 2, 3, 4, 6.)
- Self-discipline / guardrails. Research before executing, verify before reporting, reflect and learn after. Guardrails are how an agent earns autonomy. (Laws 1, 4, 5, 7.)
Skill mechanics are scaffolding around those two. The invariants are the product; the scaffolding is replaceable.
Decision Rules
| Situation | Model-forward call |
|---|---|
| A native Claude Code feature now covers what a custom skill or hook does | Prefer the native path; propose retiring the scaffold instead of maintaining a parallel one |
| A skill's instructions conflict with current Claude Code best practice | Follow Claude Code best practice; flag the skill for update |
| Tempted to add scaffolding to compensate for a model weakness | First confirm the current model still has that weakness; do not patch yesterday's model |
| A guardrail keeps firing on behavior the model no longer exhibits | Propose loosening or retiring it — stacking stale guardrails is also drift |
| The user explicitly says to go against a default | The user wins. "Until said otherwise" is the contract. |
Never retire a guardrail unilaterally — retiring scaffolding is a proposal to the operator, not a silent action. The bias points toward the model; the authority stays with the user.
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.
- 3d ago First seen · 45 lines · 62 tokens per session scan A 2e60d2bdf2cf
model-forward is a skill published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 9d ago), licensed MIT. It adds 62 tokens to every session and 650 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-08-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
clean-architecture
Structure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go"…