Skip to content
Agentmart
Submit a tool

sage-architecture-governor

Use for Sage prompt, topology, tool, planner, runtime authority, and other consequential architecture changes; keep ordinary development measurement plumbing…

Skill by MythicAgents

IndexedGPL-3.0★ 29
Write a review

Chalk Labs

Need help deploying sage-architecture-governor?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/mythicagents-sage-architecture-governor

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use for Sage prompt, topology, tool, planner, runtime authority, and other consequential architecture changes; keep ordinary development measurement plumbing within standing task authority.

Use cases: productivity, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/sage-architecture-governor
  • /tmp/sage_arch_gate
  • /tmp/sage_arch_review

What's inside

Skill name
sage-architecture-governor
Description
Use for Sage prompt, topology, tool, planner, runtime authority, and other consequential architecture changes; keep ordinary development measurement plumbing within standing task authority.
License
GPL-3.0
Instructions
63 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Files (8)

  • SKILL.md
  • openai.yaml · agents/
  • arch_governor_common.py · scripts/
  • check_arch_budget.py · scripts/
  • open_gate.py · scripts/
  • pre_tool_use_arch_gate.py · scripts/
  • review_lease.py · scripts/
  • test_review_lease.py · tests/

SKILL.md (first lines)

# Sage Architecture Governor

Use this workflow for actual architecture or authority changes. Internal evaluator plumbing does not become an
architecture change merely because its path is in the historical high-risk list.

## Choose the decision

- `runtime_bugfix`: repair a concrete production defect with focused assembled-path probes.
- `development_measurement`: an internal comparison or evaluator repair, with model/config/source identity,
  structured logs, a prospective protocol, resource limits, and independent outcome proof.
- `sealed_evaluation`: a declared final holdout, promotion/release, externally relied-on claim, or named integrity
  threat. Specify which relying decision requires stronger provenance before using the existing lease tools.

For the first two lanes, use a concise working contract: hypothesis, atomic criteria, affected path/files,
falsifying and valid-near-match probes, non-goals, complexity constraints, and a stop-loss.
Update it when production facts invalidate an assumption; version changed protocols without rewriting results.
No mandatory fresh candidate reviewer, per-repair approval, exact-hash binding, immutable bundle, or lease applies.

## Architecture approval and prompt protection

Actual prompt, topology, tool-surface, planner, or runtime authority changes require user authorization covering
that change. Existing explicit task approval can supply it; do not ask again for each in-scope repair.
When opening a prompt-edit token, briefly identify the hypothesis, scope, verification, generality risk, and
complexity tradeoff. Use the narrowest approved scope:

```bash
python3 skills/sage-architecture-governor/scripts/open_gate.py open --reason "approved change" --approved-by "user" --approval-source "applicable task approval" --minutes 90 --files 'Payload_Type/sage/prompts/**'
```

Inspect with `open_gate.py status` and close with `open_gate.py close`. A token does not grant live authority.

The project PreToolUse hook hard-denies prompt edits without a scoped token, advises on other high-risk paths,
and protects an active review lease when one was deliberately opened. Its source remains the enforcement authority.
Ordinary development measurement needs no token or lease. Do not create one merely to satisfy a historical recipe.

## Complexity and verification

- Compare a thinner verifier, retrieval, or existing data path before expanding prompts, tools, or symbolic gates.
- No new GOAD-specific strategy in product code. Declare any intended benchmark-only scope.
- Tie every changed behavior to a probe. Exercise the actual assembled producer/consumer boundary.
- After repeated tactical repairs, diagnose the mechanism and reconsider scope before adding more code.
- Run relevant tests during repairs and the full offline suite at the integration boundary.
- Use the existing budget checker for actual high-risk changes; it is advisory at session Stop:

```bash
python3 skills/sage-architecture-governor/scripts/check_arch_budget.py --changed
```

A targeted reviewer reports reproducible blocking counterexamples to the agreed claim, separately from hardening,
pre-existing, unreachable, and out-of-scope findings. Review is not a universal development pre-run prerequisite.
Source identity detects drift; it does not independently prove correctness or authenticate the producer.

## Existing tools

- `scripts/pre_tool_use_arch_gate.py`: prompt-edit protection, high-risk advisories, active lease protection.
- `scripts/open_gate.py`: scoped token lifecycle.
- `scripts/check_arch_budget.py`: architecture budget inspection.
- `scripts/review_lease.py`: optional stronger provenance for a separately justified sealed decision.

When changing these executables, run their local `--self-test` paths and the affected tests under
`skills/sage-architecture-governor/tests`. Do not run live activity to verify governance.

From MythicAgents/sage, GPL-3.0.

More from MythicAgents/sage

Signals

Stars
29
Forks
5
Open issues
1
Last commit (this folder)
Oct 20, 2026 (10 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
GPL-3.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from MythicAgents

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get sage-architecture-governor running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying sage-architecture-governor?

CallGet help
Cite this page

sage-architecture-governor skill. Agent Mart. https://agentmart.dev/skills/mythicagents-sage-architecture-governor (last updated 2026-10-24)