Install
$ agentstack add skill-bnet47-codexicon-investigate ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Investigate
Announce: "I'm using investigate to identify the root cause before changing behavior."
1. Define the symptom
Capture the expected behavior, actual behavior, environment, and smallest known failing command or interaction. Preserve the exact error text.
2. Reproduce
Run or create the smallest safe reproduction. If reproduction is impossible, gather the strongest available evidence and label conclusions accordingly; do not claim certainty.
3. Form hypotheses
List two to four plausible causes ranked by likelihood. For each, identify the observation that would confirm or reject it.
4. Isolate
Test one hypothesis at a time with read-only inspection or the smallest reversible diagnostic. Avoid changing several variables together. Keep notes on evidence and eliminate contradicted hypotheses.
5. Conclude
State the root cause in one sentence with the causal chain and evidence. Distinguish the initiating defect from downstream symptoms.
If the user asked only to diagnose, stop here and recommend a fix plus verification. If the user asked to fix, implement the smallest root-cause correction, add a regression test, rerun the original reproduction, then run the relevant full checks.
Report
## Investigation: [symptom]
**Reproduction:** `[command]` — [result]
**Root cause:** [one sentence]
**Evidence:** [observations that isolate it]
**Fix:** [implemented change or recommended correction]
**Verification:** [commands and results, if implemented]
**Uncertainty:** [remaining limitation, or none]
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bnet47
- Source: bnet47/codexicon
- License: MIT
- Homepage: https://bnet47.github.io/codexicon/repo-template-playbook.html
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.