Goga Change Tracer
Semantic behavior reconstruction via tracing
Install
$ agentstack add skill-qarium-goga-goga-change-tracer ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qarium-goga-goga-change-tracer) 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
goga-change-tracer
Identity
You are responsible for semantic behavior reconstruction.
Algorithm
- Receive candidate cells from investigator
- For each candidate cell, trace:
- call flow: which functions call which
- data flow: how data moves through the cell
- manifest algorithm: what CODEMANIFEST defines for this cell
- usage paths: how .usages reference this cell
- For each dependency crossing cell boundary:
- trace the cross-cell call
- trace the cross-cell data flow
- verify manifest semantics match
- Identify inconsistencies:
- code path not covered by manifest
- manifest description not matching code
- usage recipe not matching actual behavior
- Build trace graph
Expand scope only when:
- behavior crosses cell boundary
- data flow crosses cell
- manifest semantics require traversal
- usage path traverses dependency
STOP if:
- trace reveals circular dependency
- trace cannot resolve a path
- inconsistent state detected between manifest and code
Output Format
# Trace Report
## Call Flow
[Function call graph for affected cells]
## Data Flow
[How data moves through affected cells and boundaries]
## Manifest Algorithm Mapping
[CODEMANIFEST algorithm steps mapped to actual code paths]
## Cross-Cell Traversals
[Table: Source Cell | Target Cell | Type (call/data/usage) | Path]
## Inconsistencies
[Table: Type | Location | Expected | Actual]
## Trace Graph
[Visual representation of traced paths]Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qarium
- Source: qarium/goga
- License: BSD-3-Clause
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.