Agtx ReviewSAFE
๐๐ผโ๏ธ The blackboard for coding agents - agentic development environment for claude code, codex, cursor, opencode, grok and more.
Overview
๐๐ผโ๏ธ The blackboard for coding agents - agentic development environment for claude code, codex, cursor, opencode, grok and more.
f5762dd0b415OBSERVED ยท 2026-10-10What it tells the agent
The instruction file, verbatim from the audited commit โ this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
--- name: agtx-review description: Self-review completed work. Check for correctness, edge cases, and code quality. Write review to .agtx/review.md and stop. --- # Review Phase You are in the **review phase** of an agtx-managed task. ## Instructions 1. Pick the scope. If `.agtx/reviewed-at` exists, a prior review covered everything up to that commit: review `git diff $(cat .agtx/reviewed-at)..HEAD` plus `git status --short` for uncommitted work, and read the prior `.agtx/review.md` โ check its points were addressed, don't re-review the branch. Otherwise review all changes made during execution: `git diff HEAD` (staged+unstaged) and `git log --oneline $(git merge-base HEAD origin/HEAD)..HEAD` for your commits. Do NOT diff against `main` or `origin/main` โ those may include unrelated upstream history. Either way `??` lines in `git status --short` are untracked files that `git diff` never shows โ read them in full. 2. Check for: - Correctness and edge cases - Error handling - Code style consistency with the existing codebase - Test coverage - Security issues (injection, XSS, etc.) 3. Fix any issues you find 4. Commit them. `git add -A`, commit, verify `git status --short` clean. Uncommitted = destroyed at task completion; merge is blocked until clean. ## Output Write your review to `.agtx/review.md` in the **current working directory** with these sections: ## Review Findings from your review โ what looks good, what was fixed, any concerns. ## Status Either `READY` (good to merge) or `NEEDS_WORK` (with explanation of remaining issues). ## CRITICAL: Stop After Writing After writing `.agtx/review.md` (in the current working directory): - Say: "Review written to `.agtx/review.md`." - Wait for further instructions ## Output Style Terse. No pleasantries. Fragments OK. Short synonyms. Code exact. Status updates: one line. Pattern: [what] [why]. Done.
Trust audit
SAFEgrade B ยท trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
f5762dd0b415full audit observations/trust-audit/skill/fynnfluegge__agtx-review.json ยท Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-10 | f5762dd0b415 | SAFE | B | 89 | first audit |
Questions
What does the Agtx Review skill do?
๐๐ผโ๏ธ The blackboard for coding agents - agentic development environment for claude code, codex, cursor, opencode, grok and more.
Is Agtx Review safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Agtx Review access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (f5762dd0b415), read on 2026-10-10. The repository is watched, and a new audit runs when it changes โ this is the first audit.