Executable form of model-tiering-convention: five pre-tiered subagents with model + effort + tool scope declared in frontmatter. Triggers whenever work can be delegated instead of done on the main Opus thread — reconnaissance, summarisation, mechanical implementation, review. Ships explorer (haiku/low, read-only), summariser (haiku/low, read-only), implementer (sonnet/medium), code-reviewer (sonnet/medium, no writes), security-reviewer (opus/high, no writes). Tiering becomes mechanical instead of advisory.
0 on GitHubby Orryx Groupv0.1.0MITupdated 1 month agofoundation
/
Plugin tiered-agents from marketplace orryx-group in alexmclaren/orryx-knowledge. Commands read from the repo's manifest — 1 month ago.
What it installs
Subagents (5)
code-reviewer
Reviews a diff or branch for correctness, regressions, missing tests, and convention drift. Use before a PR or merge on ordinary changes. Escalate to security-reviewer for auth, secrets, PHI, migrations, or infrastructure.
explorer
Read-only reconnaissance across one or many repos. Use to locate files, trace call sites, enumerate conventions, or answer "where does X live" before any edit is planned. Returns findings with file:line references, not opinions.
implementer
Executes an already-decided plan or a concrete, scoped change. Use for mechanical transformation, migration writing, test writing, and any edit where the approach is settled and only the typing remains. Not for open-ended design.
security-reviewer
High-stakes review for auth, secrets handling, PHI or clinical data paths, tenant isolation and RLS, database migrations, IAM, and infrastructure changes. Use when a miss is expensive. Read-only.
summariser
Compresses files, logs, diffs, and command output into a digest so the orchestrator never loads raw content. Use for repo onboarding, long test output, large diffs, and log triage. Lossy by design.
Three-lane parallel execution pattern for the Orryx Group (Brain + Triora + Pillarworks lanes coordinated by SYNC_STATE + CONTROL_STATE). Triggers on cross-product Sprint planning, "what should each product team do this sprint", "coordinate the lanes", or "/3-lane-parallel". Originally Brain Sprint 28 pattern; promoted to cross-cutting.
Check-before-create discipline. Triggers before authoring a new skill, agent, prompt, slash command, hook, or shared schema. Consults the repo-local ASSET_INDEX.md to prevent duplication; lifted from Pillarworks's mature pattern. Reduces "we already have one of these" rework and keeps cross-product coordination cheaper.
BMAD planning workflow (Brief, Model, Architect, Develop). Triggers on greenfield feature work, product discovery, or "let's design X". Produces a PRD and Tech Spec before any implementation. Pattern adopted by Pillarworks from bmad-code-org; promoted to Orryx cross-cutting.
Two-stage code review (sonnet then opus for high-risk) with skill + subagent + slash-command surfaces. Triggers on review requests, pre-merge checks, "review this PR / diff / branch", or as the final step of plan-and-execute. Merges Triora code-reviewer + merge-review, Pillarworks review SKILL + reviewer + quality-gate agents, and Brain /review command.
Continuous Parallel Development (CPD) protocol with 5 parallel work streams (Research, Discovery, Planning, Development, Review). Triggers on Sprint planning, "run in parallel", "parallelise the work", or "what should each lane do". Defines mandatory parallel agents per sprint start, execution patterns, and research queue management. Lifted from Triora.
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of versionable .md files with a frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents alike. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, and generates conformant markdown concepts. 3 stdlib tools: scaffold_bundle (bundle scaffold), okf_linter (validates type/reserved files/links), index_generator (regenerates the index.md files). Standalone-installable; also bundled in c-level-skills. In English.
Repomix MCP server for AI-powered codebase analysis. Pack local/remote repositories and search or read the generated outputs. Foundation plugin that enables all Repomix features in Claude Code.
Produce a complete positioning document using the Dunford framework — competitive alternatives, unique attributes, value, best-fit customer, market category, positioning statement, and tagline. Use when asked to "write our positioning", "define our value prop", "positioning statement", "what market are we in", "how do we position against X", "what's our tagline", or "write our messaging foundation".
1 skill
jeremylongshore/tons-of-skills-marketplace 2,917
Maintain tiered-agents?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.