using-aegis — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited using-aegis (Agent Skill) and scored it 45/100 (orange). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 2 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.A base64 string of 128+ characters appears in a documentation file. Encoded prompt injection hides the hostile instruction in base64 — invisible to keyword filters — and relies on the agent's ability to decode it at runtime. There is no normal authoring reason to embed a multi-hundred-byte base64 blob in skill docs.
*.sig, SIGNATURES) outside the documentation.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.
<SUBAGENT-STOP>Skip for subagents.</SUBAGENT-STOP>
<EXPLICIT-MODE-GATE> If activation mode is explicit and this request did not explicitly invoke Aegis or a named skill, stay on the fast path; do not route to any Aegis skill. Explicit invocation proceeds normally. </EXPLICIT-MODE-GATE>
<EXTREMELY-IMPORTANT> You have Aegis. Load explicit/relevant Aegis skill before response/action; otherwise proceed normally. </EXTREMELY-IMPORTANT>
Understand the requested object, scope, actions, conditions, and deliverables from the conversation. Complete the authorized task within business constraints and deliver a usable, verifiable result. Project goals guide durable choices; they do not override the user's current scope. Preserve outstanding intent across follow-ups; clarify material ambiguity before dependent action and continue independent authorized work. Do not repeat satisfied approvals.
Judge success by the requested outcome. Execution, parsing, tests, and architecture alignment prove only their covered scope; tests of real acceptance criteria can prove that outcome. Fix the problem class at its owner, preserving neighboring behavior. Report delivered results and remaining gaps honestly; partial work is not complete. These are decision principles, not a new artifact, universal goal-framing route, or completion authority.
Preserve task fidelity through understanding, transformation, execution and delivery: retain decision-relevant meaning and evidence status, checking both omissions and unsupported additions. Authorized summaries, designs and evidence-based corrections are valid. Use existing checkpoints and sufficient current evidence; no extra approval, six-item report or exhaustive trace is required.
otherwise stay on the fast path. Compose ui-ux-governance for UI/UX effects; retain task ownership and scope.
README/ADR/rule/baseline sections, else a bounded index-first scan. Do not recursively read all linked docs. Non-trivial work passively use relevant CONTEXT-MAP.md/CONTEXT.md; model semantic conflicts only when found.
grill me/grill this plan/审问我/盘问我/拷问我 -> brainstorming (literal/explanatory uses do not); /aegis-goal or Aegis goal: -> goal-framing. Bug, failure, regression, or unexpected behavior routes to systematic-debugging.Medium/high: baseline read-set + plan. Spec Brief or Design Spec only for ambiguous/contract/cross-module medium/high work. TDD: off=no auto route/load; auto=risk-based strict/light/skipped; explicit strict applies. Pure explanation and read-only diagnosis skip implementation/TDD/write gates.
TaskStartSnapshot, and decides ArchitectureReviewRequired; ceremony alone never creates a branch/worktree.
non-tiny work; do not wait for the user to ask. structured trace is only for audit/debug/release/long-task review/asked and does not route (Trace Digest).
Q&A/status writes no files except authorized baseline bootstrap before code-changing advice; tiny work writes records only when required.
summary first; large input index->window->excerpt. Bound history/session/ transcript/log reads by scope/time/lines.
references/skill-discipline.md only when route/order/TDD/workspace/context re-entry/host mapping detail is needed.
Contract: only a real fast path emits Route: fast-path and an Aegis Reason Note; a routed skill owns its next-stage contract.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.