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 siva01c/claude-plugins --skill feature-workflowgit clone --depth 1 https://github.com/siva01c/claude-pluginsWrote 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/siva01c/claude-plugins/feature-workflow)<a href="https://agentmods.dev/skills/siva01c/claude-plugins/feature-workflow"><img src="https://agentmods.dev/badge/skills/siva01c/claude-plugins/feature-workflow/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/siva01c/claude-plugins/feature-workflow"><img src="https://agentmods.dev/badge/skills/siva01c/claude-plugins/feature-workflow.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.00101 | $0.01149 |
| Opus 5.5 | $0.00040 | $0.00460 |
| Sonnet 5.5 | $0.00020 | $0.00230 |
| Haiku 4.5 | $0.00010 | $0.00115 |
Grade A, and why
feature-workflow 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Workflow
A gated, phased procedure for non-trivial Drupal development tasks. The goal is that no step is skipped and no task is declared done without evidence (passing checks, exported config, green tests).
When this activates
- Building or extending a custom module or theme
- Adding routes, forms, controllers, services, or plugins
- Changing entity structure, fields, or database schema
- Any change spanning multiple files or subsystems
Task classification (do this first)
Before starting, classify the task and adjust rigor:
| Class | Signal | Rigor |
|---|---|---|
| tiny-fix | Typo, comment, CSS tweak, single-line change | Stop — use the tiny-fix skill instead |
| standard | New feature, refactor, multi-file change | All phases below |
| security-sensitive | Touches routing, forms, user input, DB queries, permissions, file handling | All phases below + mandatory security pass in Phase 3 |
| schema-touching | Changes entity definitions, fields, or DB schema | All phases below + update hook requirement in Phase 2 |
Phase 1 — Plan
- Restate the requirement in one or two sentences. If ambiguous, ask before coding.
- List the files and Drupal subsystems that will change (routing, services, config schema, hooks, plugins).
- Identify config entities the change will create or modify — these must be exported before the task is done.
- For multisite codebases: list every site that shares the affected module and note the impact.
Exit condition: a short written plan exists in the conversation. No code yet.
Phase 2 — Implement
- Follow Drupal 11 coding standards. If the
drupal-module-developmentskill (drupal-dev-tools plugin) is available, apply it; otherwise follow core conventions: dependency injection over\Drupal::static calls in OOP code, typed config schema for new config,declare(strict_types=1)where the codebase uses it. - Schema-touching tasks: every entity/field/schema change ships with a matching
hook_update_N()orhook_post_update_NAME()in the same changeset. An update hook must be idempotent. - New config objects get a
config/schema/*.schema.ymlentry. - Keep scope: do not refactor code the task did not ask for. Note improvement opportunities instead of applying them.
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 · 89 lines · 101 tokens per session scan A f9fb9adc4270
feature-workflow is a skill published in the GitHub repository siva01c/claude-plugins (16 stars, last pushed 25d ago), licensed MIT. It adds 101 tokens to every session and 1,149 once invoked, about $0.0004 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
api-security
Guideline for designing, implementing, and verifying secure APIs following OWASP API Security Top 10 (2023) best practices. Use when the user wants to: (1) review API code or design for security vulnerabilities, (2) design a secure REST, GraphQL, or gRPC API architecture, (3) implement API authentication and…
scale-to-millions
Use this skill whenever the user is designing, reviewing, debugging, or answering interview questions about system/software architecture and scalability — e.g. "scale my app", "how do I handle more traffic", "design a URL shortener / news feed / chat system", "my API is slow under load", "should I shard my database"…
offensive-api-abuse
Advanced API exploitation methodology focused on business logic abuse and sophisticated attack patterns that bypass traditional security controls. Covers business logic bypass through API call chaining and workflow manipulation. Addresses GraphQL-specific attacks including batching for credential brute-force, query…
api-security-best-practices
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities.
iflytek-hyper-tts
A text-to-speech tool that turns written text into an MP3 recording. It can use an authorized voice and adjust speaking speed, volume, and pitch.
iflytek-ocr-invoice
An image-reading tool that extracts structured information from Chinese invoices, receipts, bills, and tickets. OCR means turning text in a photo or scan into computer-readable data.