Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/FouadMagdy01/RNCopilotnpx agentmods add skills/fouadmagdy01/rncopilot/create-featureWrote 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/fouadmagdy01/rncopilot/create-feature)<a href="https://agentmods.dev/skills/fouadmagdy01/rncopilot/create-feature"><img src="https://agentmods.dev/badge/skills/fouadmagdy01/rncopilot/create-feature/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/fouadmagdy01/rncopilot/create-feature"><img src="https://agentmods.dev/badge/skills/fouadmagdy01/rncopilot/create-feature.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.00020 | $0.01580 |
| Opus 5.5 | $0.00008 | $0.00632 |
| Sonnet 5.5 | $0.00004 | $0.00316 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
create-feature 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Feature Module
Scaffold a complete feature module following the project's exact conventions.
Gather Information
Ask the user for:
- Feature name (e.g., "products", "orders", "notifications") - lowercase, plural
- Entity fields - the data shape (name, type pairs)
- API endpoint base (e.g., "/products") - defaults to
/<feature-name>
Steps
1. Create Directory Structure
src/features/<name>/
├── types/index.ts
├── services/<name>Service.ts
├── hooks/use<Name>.ts
├── schemas/<name>Schema.ts
├── constants/index.ts
└── components/ (empty directory, ready for feature components)
2. Generate Types File
// src/features/<name>/types/index.ts
export interface <Entity> {
id: string;
// ... fields from user input
createdAt: string;
updatedAt: string;
}
export interface Create<Entity>Data {
// ... writable fields (exclude id, createdAt, updatedAt)
}
export interface Update<Entity>Data extends Partial<Create<Entity>Data> {}
3. Generate Service File
// src/features/<name>/services/<name>Service.ts
import { api } from '@/services/api';
import type { <Entity>, Create<Entity>Data, Update<Entity>Data } from '../types';
export async function fetch<Entities>(): Promise<<Entity>[]> {
const { data } = await api.get<<Entity>[]>('<endpoint>');
return data;
}
export async function fetch<Entity>(id: string): Promise<<Entity>> {
const { data } = await api.get<<Entity>>(`<endpoint>/${id}`);
return data;
}
export async function create<Entity>(payload: Create<Entity>Data): Promise<<Entity>> {
const { data } = await api.post<<Entity>>('<endpoint>', payload);
return data;
}
export async function update<Entity>(id: string, payload: Update<Entity>Data): Promise<<Entity>> {
const { data } = await api.patch<<Entity>>(`<endpoint>/${id}`, payload);
return data;
}
export async function delete<Entity>(id: string): Promise<void> {
await api.delete(`<endpoint>/${id}`);
}
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.
- 1mo ago First seen · 225 lines · 20 tokens per session scan A 6e293b4259d9
create-feature is a skill published in the GitHub repository FouadMagdy01/RNCopilot (43 stars, last pushed 7mo ago), licensed MIT. It adds 20 tokens to every session and 1,580 once invoked, about $0.0001 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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…