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 alieismy/codex-three-layer-delivery --skill rd-feasibilitygit clone --depth 1 https://github.com/alieismy/codex-three-layer-deliveryWrote 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/alieismy/codex-three-layer-delivery/rd-feasibility)<a href="https://agentmods.dev/skills/alieismy/codex-three-layer-delivery/rd-feasibility"><img src="https://agentmods.dev/badge/skills/alieismy/codex-three-layer-delivery/rd-feasibility/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/alieismy/codex-three-layer-delivery/rd-feasibility"><img src="https://agentmods.dev/badge/skills/alieismy/codex-three-layer-delivery/rd-feasibility.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.00074 | $0.01123 |
| Opus 5 | $0.00037 | $0.00562 |
| Sonnet 5 | $0.00015 | $0.00225 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
rd-feasibility 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rd-feasibility
Produce decision-ready feasibility studies that distinguish confirmed facts, assumptions, estimates, and unresolved verification needs.
Deliverables
- Feasibility study / feasibility analysis report
- Feasibility comparison matrix
- Recommended conclusion: feasible / conditionally feasible / not feasible
- Risk register with mitigation and verification actions
Execution Steps
1. Study Scope Confirmation
- Clarify the decision question: what needs to be judged feasible or infeasible
- Identify the target audience: decision-makers, project approval committee, client reviewers, technical leadership
- Confirm input sources: PRD, meeting notes, existing system documents, standards, policies, budgets, schedules
- Separate facts from assumptions before evaluating feasibility
Completion criterion: the decision question, comparison scope, audience, source set, facts, assumptions, and evidence gaps are explicit.
2. Feasibility Dimensions
Evaluate the option or project across these dimensions:
| Dimension | Check Content |
|---|---|
| Necessity | problem value, policy/business driver, stakeholder demand |
| Technical feasibility | maturity, compatibility, integration constraints, data availability, architecture fit |
| Economic feasibility | budget, lifecycle cost, licensing, staffing, procurement |
| Schedule feasibility | milestones, dependencies, review cycles, delivery risks |
| Operational feasibility | installability, maintainability, staffing model, process fit, training, support and rollback |
| Security and compliance | regulations, standards, privacy, supply-chain exposure, security controls, auditability |
| Sustainability | upstream maintenance, release cadence, licensing, vendor or community dependency, exit path |
| Risk feasibility | high-risk assumptions, external dependencies, failure modes, fallback options |
Completion criterion: every material dimension is assessed against evidence or explicitly excluded with a reason; no missing dimension is silently treated as favorable.
What ships with it
3 files 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 · 116 lines · 74 tokens per session scan A e9d21ea5b171
rd-feasibility is a skill published in the GitHub repository alieismy/codex-three-layer-delivery (2 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 1,123 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…