Install
$ agentstack add skill-adeerkhan-vitruvius-audit ✓ 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
Engineering Audit
Audit a claimed/specified behavior against its actual implementation or source. This reuses the engineering-research discipline, focused on consistency between two things.
Workflow
- Outline the audit — what is being compared (paper vs code, spec vs
design, standard vs as-built, datasheet vs application), which claims to check, and the governing references. Write the plan to outputs/.plans/.md; briefly summarize and continue.
- Read both sides directly — the claim AND the implementation/source.
For code: read the actual code, not the README. For a standard: read the actual provision. Record versions/editions/commits.
- Compare claim-by-claim — for each checked item record:
- the claim (with its source location)
- the actual behavior (with its location)
- match / mismatch / missing / ambiguous
- Call out — missing code or provisions, mismatched defaults, ambiguous
parameters, claims that outrun the evidence, and reproduction risks.
- Save one audit report to
outputs/-audit.md, ending with a
Sources section (paper + repo URL, spec + section, standard + edition).
Never conclude "consistent" from a skim. Every claim in the audit's verdict must name the exact provision, line, or commit it was checked against.
Scope and Boundaries
- This skill produces research — it does NOT produce final designs or construction documents.
- Research-only, not for final engineering sign-off. Licensed engineers must review and approve any design based on this research.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: adeerkhan
- Source: adeerkhan/vitruvius
- License: MIT
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.