terra4mice — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited terra4mice (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.
Manage spec-driven development convergence for Execution Market. Use when the user says "terra4mice", "convergence", "check progress", "what's missing", "mark as done", "refresh state", or wants to track implementation status against the spec.
| Action | Command |
|---|---|
| See what needs work | terra4mice plan |
| Scan codebase | terra4mice refresh |
| Mark resource done | terra4mice mark <resource> -s implemented |
| Mark + lock (survives refresh) | terra4mice mark <resource> -s implemented --lock |
| Lock existing resource | terra4mice lock <resource> |
| Unlock resource | terra4mice unlock <resource> |
| Mark resource partial | terra4mice mark <resource> -s partial |
| List all resources | terra4mice state list |
| Show one resource | terra4mice state show <resource> |
IMPORTANT: Always run commands from project root (/mnt/z/ultravioleta/dao/execution-market).
Resources can be locked to prevent refresh from overwriting them. This eliminates the need to re-mark external/manual items after every refresh.
# Lock when marking (recommended for external items)
terra4mice mark contract.x402r_escrow -s implemented --lock
# Lock an existing resource
terra4mice lock expansion.erc8004_base_registration
# Unlock if you want refresh to re-scan it
terra4mice unlock expansion.erc8004_base_registration
# State list shows [locked] indicator
terra4mice state list # locked items show cyan [locked] tagWhen to lock:
When NOT to lock:
# 1. See overall convergence
terra4mice plan
# 2. If stale, refresh from codebase (locked items are preserved)
terra4mice refresh
# 3. Check plan again — no need to re-mark locked items!
terra4mice plan# 1. Implement the feature (write code, tests, etc.)
# 2. Run refresh to auto-detect file-based resources
terra4mice refresh
# 3. If the feature is external (ECS, on-chain, live test), mark + lock:
terra4mice mark <resource_name> -s implemented --lock
# 4. Verify with plan
terra4mice planterra4mice.spec.yaml — add the resource under the appropriate sectionterra4mice plan — it will show the new resource as "to create"terra4mice refresh or terra4mice mark <resource> -s implementedIf files exist for a resource, refresh marks it "implemented" even if functionality is incomplete. Either:
terra4mice mark <resource> -s partial --lockterra4mice.spec.yaml (project root)terra4mice.state.json (project root, auto-managed)Lock protects the entire resource from refresh. If you want refresh to update files/symbols but not status, you'll need to unlock, refresh, then re-lock.
Contracts (5): x402r_escrow, usdc_base, deposit_relay_factory, deposit_relay, vault Expansion (7): erc8004_base_registration, gasless_agent_registration, gasless_worker_registration, identity_metadata_api, multichain_identity_verification, task_network_field, task_token_field TODOs (4): d04_register_agent_on_base, d11_submission_form_rls, fee_rounding_fix, admin_dashboard_deploy
| Metric | Value |
|---|---|
| Total resources | 109 |
| Implemented | ~93 |
| Missing | ~16 (to create) |
| Convergence | 85.3% |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.