npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ai-agent-forge/plugin-decision-escalation

v0.88.28

Published

Decision escalation capability plugin for Agent Forge (formal fork-decision ask with a local confirmation page, timeout de-escalation to an independent adjudication chain, and an irreversible redline)

Readme

@agent-forge/plugin-decision-escalation

Decision escalation capability plugin for Agent Forge: a formal ask channel for forks — the model asks with decision_ask, the user answers on a local confirmation page or in TUI text, and an unattended fork never stalls forever: reversible levels are adjudicated by an independent subagent chain on timeout, irreversible ones stay stopped.

  • Design contract (authoritative): docs/design/决策升级插件设计.md
  • Position: a decision channel alongside the goal/plan/todo layers; the main agent keeps L0 (trivial fork) autonomy — this plugin only takes over when a fork is worth a formal ask.

Levels (设计 §3)

| Level | Verdict | On timeout | | --- | --- | --- | | L0 | reversible, local impact | not this plugin's business | | L1 (routine) | reversible, single module | one independent adjudicator agent | | L2 (significant) | reversible but directional | one advocate per reversible option + independent judge | | L3 (redline) | any option reversibility: "irreversible" or field missing | never adjudicated — stays stopped, fork written back to the user |

The redline is engine-derived from per-option reversibility, never the model's risk self-assessment; risk_class only picks L1 vs L2 handling.

Tools

| Tool | Purpose | | --- | --- | | decision_ask | Ask a fork (2..4 closed options + symmetric context_digest brief + risk_class). Returns decisionId, page URL, timeoutMs, riskClass, redLine immediately; non-blocking. | | decision_resolve | Book the answer: source: "user" (page or TUI text) or source: "adjudication" — the latter only when an injected verdict exists and matches; fabricating one is rejected. |

Command: /decision log [N] · /decision show <id> · /decision cancel <id>.

Timeout de-escalation (设计 §5)

Factory default 180s (config.timeoutMs overrides). On timeout without a user answer: redline forks inject a decision.notice halted notice; L1/L2 forks dispatch the adjudication chain through the public agent-forge.agent-task-scheduler@1 capability (subagent-delegate), readonly profile with read/grep/ls/find only. Every chain failure — capability missing, submit/drain error, subagent not succeeded, output violating the {"choice","confidence","rationale","keyEvidence"} JSON protocol — lands as adjudication.unavailable / adjudication.unparseable and the same halted behavior: stop, no retry, no silent downgrade.

Persistence protocol

Structurally identical to the goal/plan/alignment plugins: append-only decision.state full snapshots plus one decision.transition audit entry per conversion (asked | answered.user | answered.adjudication | timed-out.halted | timed-out.adjudicating | adjudication.unavailable | adjudication.unparseable | cancelled), announced as decision.changed. The full adjudication verdict rides the decision.state snapshot for /decision show. User answers inject as decision.answered (display: false, model context); notices inject as decision.notice (display: true, user visible).

Notes

  • Requires a host session that exposes SessionAPI.sendMessage (answer and notice injection); without it decision_ask fails fast and the rest of the surface stays usable.
  • The confirmation page is one of two answer channels for a present user; unattended sessions never depend on it.
  • Deterministic tests only (fake CapabilityAPI + fake scheduler handle + real node:http on an OS-assigned port); no real model calls. Adjudication quality is a model quality attribute and deliberately untested (设计 §9).