Borrowing it
Nothing to install: this file belongs to vinilana/invokta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vinilana/invokta/main/.agents/skills/invokta-delivery/SKILL.mdgit clone --depth 1 https://github.com/vinilana/invoktaWrote 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/vinilana/invokta/invokta-delivery)<a href="https://agentmods.dev/skills/vinilana/invokta/invokta-delivery"><img src="https://agentmods.dev/badge/skills/vinilana/invokta/invokta-delivery/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/vinilana/invokta/invokta-delivery"><img src="https://agentmods.dev/badge/skills/vinilana/invokta/invokta-delivery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.00710 |
| Opus 5 | $0.00028 | $0.00355 |
| Sonnet 5 | $0.00011 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
invokta-delivery 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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invokta Delivery
Prepare the delivery
- Read
docs/README.mdand locate the milestone indocs/implementation-plan-and-acceptance-criteria.md. - Compare the milestone with
docs/vision-and-invariants.md,docs/architecture.md,docs/scope-and-limits.md,docs/adr/README.md, applicable ADRs, public contracts, and acceptance tests. Treat these sources as authoritative; do not duplicate their detail in this skill. - Inspect the code, tests, and Git state before editing. Preserve unrelated changes and exclude unrelated files from the work item.
- Define a small vertical slice: observable behavior, acceptance criterion, affected components, and validation command.
Stop and request a decision when authoritative documents conflict, acceptance criteria are not testable, or implementation requires expanding the contract or architecture.
Apply the gates
Gate 1 — Scope and contract
- Map each acceptance criterion to at least one observable test.
- Confirm inputs, outputs, errors, invariants, and limits before changing the implementation.
- Preserve public contract compatibility. Require an explicit decision for any breaking change.
- Apply
$invokta-contract-reviewbefore coding when the milestone creates or changes an API, schema, port, event, public error, or operational limit.
Gate 2 — RED
- Write the smallest test that demonstrates the missing behavior or bug first.
- Run the test and confirm that it fails for the expected reason, not because of an environment, fixture, or syntax error.
- Record the RED evidence in the delivery summary.
Do not proceed without a valid RED result unless the change is strictly documentation or tooling with no executable behavior. Explain the exception.
Gate 3 — GREEN and REFACTOR
- Implement only what the test and contract require.
- Follow the dependency direction, ports, adapters, and boundaries defined by the ADRs.
- Avoid architectural shortcuts, global dependencies, validation bypasses, and premature abstractions.
- Run the focused test until it passes. Refactor without changing behavior, then run it again.
What ships with it
1 file 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.
- 10d ago First seen · 65 lines · 57 tokens per session scan A 581eea7d1213
invokta-delivery is a skill published in the GitHub repository vinilana/invokta (129 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 710 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-30.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
cmux-testing
A regression test for a bug fix ships as two commits so CI proves the test catches the bug.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
quick
/quick — Lightweight Feature Workflow.