implementation

implementation is a skill for Claude Code, Codex from Miosa-osa/OSA. It costs 40 tokens per session (340 once invoked), scanned A, original, Apache-2.0.

A coding workflow for fully implementing a requested feature or change in an existing codebase.

In plain words
What is it for?
Use it when you need to build a feature, modify software behavior, or complete a multi-file coding task.
Why use it?
It helps turn a specification and its acceptance requirements into working changes across the necessary files.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when you need to build a feature, modify software behavior, or complete a multi-file coding task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/miosa-osa/osa/implementation
Install

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.

Any agent
npx skills add Miosa-osa/OSA --skill implementation
Clone the repo
git clone --depth 1 https://github.com/Miosa-osa/OSA

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for implementation

README.md
[![agentmods](https://agentmods.dev/badge/skills/miosa-osa/osa/implementation/github.svg)](https://agentmods.dev/skills/miosa-osa/osa/implementation)
Your own site
<a href="https://agentmods.dev/skills/miosa-osa/osa/implementation"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/implementation/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.

agentmods 80×15 button for implementation

Your own site · 80×15
<a href="https://agentmods.dev/skills/miosa-osa/osa/implementation"><img src="https://agentmods.dev/badge/skills/miosa-osa/osa/implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 340 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.00340
Opus 5.5 $0.00016 $0.00136
Sonnet 5.5 $0.00008 $0.00068
Haiku 4.5 $0.00004 $0.00034

Measured 1mo ago against content hash e53cdac77896, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implementation 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 1mo 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.

priv/skills/implementation/SKILL.md · 43 lines

What it actually says

Implementation

Deliver the requested behavior through the codebase's existing seams and conventions.

Procedure

  1. Extract concrete requirements, constraints, and acceptance evidence.
  2. Read project instructions and the smallest relevant slice of architecture.
  3. Identify the module interface that should own the behavior.
  4. Find analogous code and tests before designing a new pattern.
  5. Create a task list for work with three or more dependent steps.
  6. Implement in vertical slices that can be verified independently.
  7. Add or update tests at the interface where callers observe the behavior.
  8. Run focused checks after each slice, then the proportionate broader suite.
  9. Inspect the final diff for accidental scope, generated files, secrets, and user-owned changes.
  10. Audit every requirement against current evidence before claiming completion.

Design posture

  • Prefer one deep module with a small interface over logic spread across callers.
  • Preserve existing conventions unless they are the cause of the requested change.
  • Do not silently narrow the request to what is easiest to test.
  • Keep configuration, enforcement, and displayed state sourced from the same authority.
  • Do not modify unrelated dirty files.
Changes

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.

  1. 1mo ago First seen · 43 lines · 40 tokens per session scan A e53cdac77896

Subscribe to this mod's changes

implementation is a skill published in the GitHub repository Miosa-osa/OSA (78 stars, last pushed 11d ago), licensed Apache-2.0. It adds 40 tokens to every session and 340 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-30.