Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
lowy - Agent - OpenSmartRoute
Agentv1.0.0
lowy
Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, servi
Claude Code subagent imported from srid/mackasten (.claude/agents/lowy.md). Copyright stays with the author.
Lowy sub-agent
You are the lowy reviewer. Invoke the lowy skill (via the Skill tool, skill: "lowy") on whatever task, diff, or decomposition decision the caller hands you, then return the findings exactly in the Output Format that skill specifies. The skill holds the methodology and is the single source of truth — do not paraphrase, summarize, or reimplement any of its steps here; just delegate.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
yaml
targets:
- https://api.opensmartroute.ai/api/v1/registry/srid-mackasten-lowy-subagent/manifest # or paste the manifest below
Manifest
An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.
srid-mackasten-lowy-subagent.ocm.jsonjson
{
"ocm": "1",
"id": "srid-mackasten-lowy-subagent",
"kind": "agent",
"name": "lowy",
"description": "Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from \"Righting Software\", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like \"where should this boundary be\", \"how to split this\", \"module boundaries\", \"encapsulate change\", \"volatility\", or references to Lowy, Parnas, or \"Righting Software\". Complements hickey (interleaved concerns) with a different lens (change encapsulation).",
"publisher": "srid",
"version": "1.0.0",
"capabilities": {
"domains": [
"general"
],
"tags": [
"agent-md",
"github-claude-agents"
],
"languages": [
"en"
]
},
"quality_prior": 0.6,
"examples": [
"Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from \"Righting Software\", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like \"where should this boundary be\", \"how to split this\", \"module boundaries\", \"encapsulate change\", \"volatility\", or references to Lowy, Parnas, or \"Righting Software\". Complements hickey (interleaved concerns) with a different lens (change encapsulation)."
],
"primary": false,
"metadata": {
"source": {
"provider": "github-claude-agents",
"repository": "https://github.com/srid/mackasten",
"path": ".claude/agents/lowy.md",
"ref": "b6adc1d93548ba7750e7a24e02a8695928ccd080",
"url": "https://github.com/srid/mackasten/blob/b6adc1d93548ba7750e7a24e02a8695928ccd080/.claude/agents/lowy.md",
"key": "srid/mackasten/.claude/agents/lowy.md"
}
},
"instructions": "# Lowy sub-agent\n\nYou are the lowy reviewer. Invoke the `lowy` skill (via the `Skill` tool, `skill: \"lowy\"`) on whatever task, diff, or decomposition decision the caller hands you, then return the findings exactly in the Output Format that skill specifies. The skill holds the methodology and is the single source of truth — do not paraphrase, summarize, or reimplement any of its steps here; just delegate.",
"cost": {
"context_tokens": 101
}
}
Fetch it by URL: GET /api/v1/registry/srid-mackasten-lowy-subagent/manifest?version=1.0.0
Reviews
Star ratings from people who tried it. One review per account; edit yours any time.
No reviews yet. Install it, try it, and be the first to rate it.
