Which agents work with it?

Any agent that reads skills from a directory. Claude Code, Codex and Gemini CLI read it natively; Cursor and VS Code connect over MCP.

The voice runs on your own machine, so there is nothing to meter. The first run downloads it, about 340 MB.

Yes. The skill is MIT-licensed and the authoring format is public.

gstack's /cso stops reading its own file names as leaked secrets

2 hours ago

@gstack Subscribe

gstack 1.91.135.0 to 1.91.136.0: /cso evaluation repair runs stop failing when the secret redactor mistakes the helper's own file names for credentials, and /cso release qualification counts a tested claim as false only when trusted evidence could have proven it. 1.91.135.0 notes: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911350---2026-10-18 1.91.136.0 notes: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1911360---2026-10-18

Ask

Ask about this presentation

Answers are generated from this presentation.

Show transcript

Redaction

gstack's /cso repair runs stop failing on the helper's own file names

<finding id>-before-<plan hash>.jsonREDACTION_FAILED

Now a known helper-ID shapepasses

Any other word in that spot still goes through the secret redactor.

RedactionTested claimsUnchangedYour repo

garrytan/gstack · CHANGELOG.md 1.91.135.0

When a gstack /cso evaluation ran a repair, the secret redactor read the finding ID in the helper's own file names as a credential, and failed the whole cell. Those names now pass. Anything else still gets redacted.

Tested claims

/cso counts a tested claim as false only when it could have been proven

Claim on the evaluator's own fixture instrumentationcounts neither way

Claim on a real incidental issueneeds a passing replay

12 of the 33 claims counted falsely tested sat on fixture instrumentation.

RedactionTested claimsUnchangedYour repo

garrytan/gstack · CHANGELOG.md 1.91.136.0

In /cso's release qualification, twelve of the thirty-three claims marked falsely tested sat on the evaluator's own fixtures. Those now count neither way. A claim on a real incidental issue needs a passing replay of its signed repair.

Unchanged

Every other /cso bar stays where it was

Recall and repair, including held-out repair

The v2 baseline and every threshold

A malformed or reused replayEvidenceHash is rejected

RedactionTested claimsUnchangedYour repo

garrytan/gstack · CHANGELOG.md 1.91.136.0

The rest of the bar stays put. Recall, repair, held-out repair, the version two baseline and every threshold still need the seeded issue. A malformed or reused replay hash is rejected.