custom-engine — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited custom-engine (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This directory is a minimal skill-up fixture that exercises the Custom Engine local and http transports end-to-end. It is consumed by e2e/custom_engine_test.go.
agent.sh + evals/eval.yaml cover the local transport: agent.sh is a deterministic stand-in for a real custom agent that reads the SessionInput JSON the framework writes to ${input_file} and emits a fixed SessionResult on stdout. The case asserts that final_message flows from the agent's stdout into the report.
evals/eval-http.yaml exercises the http transport against the same hello.yaml case. TestPipeline_CustomEngine_HTTPTransport starts an in-process httptest server, points ${CUSTOM_AGENT_ENDPOINT} at it, and asserts the posted SessionInput reaches the server and the returned SessionResult flows into the report — so the http stand-in agent lives in the test rather than in agent.sh.
The eval-stateful-*.yaml fixtures exercise opt-in stateful conversations for both transports, including session-ID propagation, per-turn post-conditions, capture, substitution, and a final response that needs no continuation ID.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.