Borrowing it
Nothing to install: this file belongs to SioYooo/RepoGrammar. 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/SioYooo/RepoGrammar/main/.agents/skills/major-feature-workflow/SKILL.mdgit clone --depth 1 https://github.com/SioYooo/RepoGrammarWrote 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/sioyooo/repogrammar/major-feature-workflow)<a href="https://agentmods.dev/skills/sioyooo/repogrammar/major-feature-workflow"><img src="https://agentmods.dev/badge/skills/sioyooo/repogrammar/major-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/sioyooo/repogrammar/major-feature-workflow"><img src="https://agentmods.dev/badge/skills/sioyooo/repogrammar/major-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.00034 | $0.00365 |
| Opus 5.5 | $0.00014 | $0.00146 |
| Sonnet 5.5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
major-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 2mo 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.
What it actually says
Purpose
Keep large changes reviewable and mergeable.
Trigger conditions
Use for new CLI commands, MCP tools, database schema changes, language or framework adapters, major indexing changes, public API changes, or cross-subsystem features.
Required reading
docs/development/branching-and-commits.mddocs/development/agent-workflow.md- Relevant ADRs and specifications
Preconditions
mainis clean or unrelated changes are explicitly protected.- The feature has a clear scope and success criteria.
Step-by-step procedure
main
-> create dedicated branch
-> implement atomic commits
-> run full verification
-> update docs and ADRs
-> review diff
-> merge --no-ff into main when checks pass
-> delete the merged branch after main contains it
Required verification
Run all standard checks before merge and again on main after merge. Before
deleting the merged branch, verify main contains the work by ancestry,
patch-equivalence, PR merge state, or another explicit branch-containment check.
Documentation updates
Update specifications, architecture docs, ADRs, README, CHANGELOG, skills, and memories as appropriate to the feature.
Commit requirements
Use one or more independently coherent Conventional Commits.
Completion report
Report feature branch, commit hashes, merge commit, branch deletion status, verification results, and remaining risks.
Failure and rollback handling
Do not merge a failing branch. Do not force-push or rewrite shared history without explicit maintainer approval.
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.
- 2mo ago First seen · 64 lines · 34 tokens per session scan A d9ee18d8f2bd
major-feature-workflow is a skill published in the GitHub repository SioYooo/RepoGrammar (0 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 365 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-31.
Other skills, from other repositories
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
gmail-sync
API integration skill that fetches Gmail messages, syncs inbox labels, and processes attachments via the Gmail REST API. Use when fetching new emails, syncing inbox state, triaging unread messages, exporting mail data, or integrating Gmail into automated workflows.
reflect
Use Recall Reflect to review AI coding workflow history as a conversation-first timeline and discuss observed patterns before changing behavior. Trigger when the user asks to reflect on a project, review AI coding workflow, inspect workflow friction, discuss repeated corrections, review handoffs, or explore possible…
rust-axum-service
Use when building or extending a Rust service - axum on tokio (or the repository's actix-web / rocket), typed errors with IntoResponse, serde at the boundary, sqlx queries and migrations, never blocking the runtime, tracing, clippy.
convex-migration-helper
Plans and executes safe Convex schema and data migrations using the widen-migrate-narrow workflow and the @convex-dev/migrations component. Use this skill when a deployment fails schema validation, existing documents need backfilling, fields need adding or removing or changing type, tables need splitting or merging…
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…