37,021 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Stack-agnostic agent skills for a disciplined, doc-driven feature/issue workflow: design, plan, execute by phases, review, audit, and ship — with a full internal review pack and merge gates.
★not rated 22
changed 1mo agoA
tokens not measured
originalMIT
Apply architectural guardrails when building software. Runs an intake questionnaire to determine the project's tier, then enforces security, reliability, and best practice rules appropriate to the tier while writing code.
Customer discovery that does not invent quotes. Turns one interview into a structured snapshot with every quote verified against the transcript, then runs the full cycle: frame, interview, synthesize, package.
★not rated 22 27d agoA
tokens not measured
originalMIT
Assesses a legacy .NET codebase and produces a pragmatic, incremental modernization roadmap — from .NET Framework to modern .NET, monolith to modular, and toward testability, DI, async, and current patterns — prioritized by risk and value. Use when the user wants to modernize legacy code, migrate from .NET Framework…
Generates a project closure report aggregating data from charter, plan-fact report, risk register, and lessons learned. Last artifact of the Closing phase. Summarizes project outcomes, deviations, realized risks, and lessons.
A Chinese-language multi-agent decision system that asks 20 themed fictional or public-forum personas to analyze a question in parallel, then combines their views into one report.
An evidence-graded library of agent-executable thinking-method skills (premortem, problem restatement, and more). Each skill is reduced to its working mechanism, graded honestly on how strong its evidence actually is, and produces a concrete artifact rather than prose. Use to reframe a problem, challenge assumptions…
A Chinese-language workflow for turning raw customer notes, emails or chat messages into a structured list of project requirements. It separates business, feature, technical and non-functional needs, and marks their priority and dependencies.
A planning guide for a public security and trust section on a SaaS or developer-tool website. It covers the site structure, page notes, evidence links, owners, and information gaps.
A cheaper sub-agent maps the code a task needs, saving the lead model's context and search tokens. Use before broad research in unfamiliar code; skip when a focused read or a current report is enough.
Run the strategy stage for one project — re-derive the project's own judged buyers, problems, and statistics from the original research records, build multiple high-level strategies the owner picks among, fan the options inside the picked strategy, then write the three plan files (Reader.md, Brief.md, Proof.md) the…
Orchestrates 6-phase SDLC pipeline (discovery, requirements, architecture, workstreams, implementation, summary) for guided feature development. Use when user runs /core:develop command, requests spec-driven development, wants to create implementation plans with architecture decisions, or mentions "SDLC"…
Interview the developer about their Ruby on Rails project (app type, database, frontend stack, background jobs, deployment target, traffic profile, compliance, current Rails version) and then route to the right downstream rails-skills. Use at the start of any new Rails work session, when the user says they want to…
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
★not rated 21 8mo agoA20 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: