Shiftblame
以時序制衡約束 agent——主對話連續承載全部工作狀態，G1/G2/G3 兩兩雙向一致才放行；放行前、判決前與收斂複驗三時點強制外部子代理對抗檢閱，複核結論強制出處綁定與反向對抗；純技術無法可靠裁定時另強制唯讀技術意見，主對話複核後自行裁定，不得轉嫁給老闆。
Works with: Claude Code (native)
native: this artifact type is that client's own format
Category: Dev Tools & CI — see all ranked ›
Install (Claude Code):
/plugin marketplace add teps3105/shiftblame
/plugin install shiftblame@shiftblame- tashan score: 46.0
- Adoption: 1 repos
- Freshness: 98.0
- Evidence coverage: 59% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- GitHub stars: 2
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
Shiftblame scores 46 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.
Show your score
source ↗ · plugin:teps3105/shiftblame/shiftblame
Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.
Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.
Measured 2026-09-12 · scorer s5 · how · something wrong here?