Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

sorawit-w/agent-skills

https://github.com/sorawit-w/agent-skills · scanned 2026-06-16 00:18 UTC (2 months, 2 weeks ago)

15 raw signals (0 security + 15 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 15 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 15 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 3 Medium 6 Low 4 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 15 Crowd 0 Layer: Frontend 2 Security 3 Cicd 1 Quality 9

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 70.3/100 with 77.8% coverage. It contains 333 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 15 findings — concentrated in quality (9), security (3), frontend (2). Risk profile is high: 0 critical, 3 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 13 of 15 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: skills/ai-eval-review/SKILL.md

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

skills/ai-eval-review/SKILL.md:132 SecretsSkill file

high System graph security security conf 1.00 Insecure pattern 'eval_used' in skills/ai-eval-review/README.md:97

Found a known-risky pattern (eval_used). Review and replace if possible.

skills/ai-eval-review/README.md:97 Eval used

high System graph security security conf 1.00 Insecure pattern 'eval_used' in skills/ai-eval-review/SKILL.md:96

Found a known-risky pattern (eval_used). Review and replace if possible.

skills/ai-eval-review/SKILL.md:96 Eval used

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/define/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

skills/define/SKILL.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/wear-the-hat/SKILL.md

skills/wear-the-hat/SKILL.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: skills/whoami/SKILL.md

skills/whoami/SKILL.md VerificationSkill file

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing ci, tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

CI/CD securityCoverage

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 2 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 14 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 Stray `console.log` in TS/JS — skills/coding-rules/resources/scripts/validate-agent-context.ts:50

Replace with the toast helper, an error boundary, or remove. `console.warn` / `console.error` are acceptable. Why: Hygiene — easy to leak debug output. Rule id: fq.console-leak

Fq console leak

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/d276b78e-c3ef-49e0-97ae-4e398d5466b7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d276b78e-c3ef-49e0-97ae-4e398d5466b7/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.