Create creator publishing checklists for social posts, videos, newsletters, podcasts, sponsored content, and campaigns. Use when Codex is asked to prepare a pre-publish QA checklist, review captions, assets, disclosures, links, tags, metadata, or post-launch checks.
Create QA matrices for features, releases, platforms, browsers, devices, roles, permissions, and risk areas. Use when Codex is asked to organize test coverage, release QA, compatibility checks, or risk-based validation into a matrix.
Design, audit, and improve QA and test strategy for software, games, websites, products, and launches. Use when Codex is asked about test plans, acceptance tests, regression, smoke testing, exploratory testing, automation scope, risk-based coverage, test data, release gates, defect triage, QA checklists, or…
Draft creator rate cards and pricing structures for sponsorship discussions. Use when Codex is asked to create influencer rate cards, pricing tables, package rates, usage-rights pricing notes, add-on pricing, or rate rationale from supplied creator inputs.
Design backend API rate limits, quotas, throttling, and abuse controls. Use when Codex is asked to define limits by user, tenant, token, IP, endpoint, plan, or workload, including headers, errors, retries, and operational monitoring.
Audit, diagnose, and optimize React and Next.js application performance. Use when Codex is asked about Core Web Vitals, slow interactions, bundle size, caching, Server Components, Client Component boundaries, re-renders, memoization, image/font/script optimization, lazy loading, route performance, production…
Improve README files for open-source projects, libraries, tools, and skill repositories. Use when Codex is asked to rewrite, audit, restructure, or strengthen a README with clearer positioning, install steps, usage examples, validation, roadmap, or contribution guidance.
Plan regression checks for bug fixes, features, refactors, and release candidates. Use when Codex is asked to identify regression risk, define a regression test plan, verify a fix, choose smoke tests, or decide what must be retested after a code change.
Plan, audit, and execute release and launch readiness for software, games, websites, products, campaigns, and public launches. Use when Codex is asked about release checklists, launch plans, deployment risk, feature flags, rollout plans, rollback plans, monitoring, support readiness, communications, incident response…
Draft user-facing release notes for software, libraries, skillsets, and documentation releases. Use when Codex is asked to write release notes, summarize changes for a version, distinguish highlights from fixes, or prepare publication notes.
Assess engineering release risk and readiness. Use when Codex is asked for a go/no-go recommendation, rollout risk, release checklist, deployment readiness, rollback plan, monitoring plan, migration risk, or production change review.
Draft creator sponsorship renewal pitches and follow-up partnership proposals. Use when Codex is asked to turn campaign results into a renewal pitch, upsell proposal, follow-up email, longer-term partnership idea, or next-campaign recommendation.
Draft safe customer support replies. Use when Codex is asked to write, review, or improve a support response, customer update, troubleshooting reply, policy-aware answer, apology, follow-up question, or success/support communication that needs human approval before sending.
Plan or interpret retention analyses for products, subscriptions, customers, accounts, or users. Use when Codex is asked to define retention, churn, repeat usage, renewal, engagement, survival curves, or retention improvement analysis.
Create and maintain executive risk registers and opportunity registers. Use when Codex is asked to identify strategic, operating, financial, customer, product, people, legal, security, delivery, or reputation risks; prioritize risks; define mitigations; or prepare leadership risk review artifacts.
Create rollback and fallback plans for deployments, releases, migrations, feature flags, and production changes. Use when Codex is asked to define rollback triggers, recovery steps, data restore needs, communication, or post-rollback validation.
Produce safe install recommendations for agent skills and skillsets. Use when Codex is asked whether a skill is safe to install, how to install with least privilege, what to inspect before install, or what approval conditions are required.
Plan, write, and review ethical B2B/B2C prospecting and outbound outreach. Use when Codex is asked about prospect lists, ICP targeting, cold email, cold calls, LinkedIn/social selling, outreach sequences, personalization, lead qualification, reply handling, objection replies, deliverability, consent, or compliant…
Write realistic routing and evaluation scenarios for agent skills and skillsets. Use when Codex is asked to add tests under tests/scenarios, define expected skill routing, create scenario prompts, or turn bundle use cases into scenario coverage.
Review scripts bundled with agent skills for permission and execution risk. Use when Codex is asked to inspect skill scripts, shell commands, file writes, destructive operations, dependency installation, or elevated permission requirements.
Review how agent skills handle secrets and credentials. Use when Codex is asked to inspect skills, scripts, examples, logs, templates, or MCP/tool instructions for secret access, redaction, storage, exposure, or approval requirements.
Design backend service boundaries and module responsibilities. Use when Codex is asked to split services, define module boundaries, choose ownership, separate domains, design integration points, or avoid coupling in backend systems.
★not rated 1 8d agoA44 tokens
originalMIT
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: