📦

unlazy

Name: unlazy
Author: leonxlnx

v2.0.0 コンテンツリビジョン r1 高リスク 📁 ファイルシステムへのアクセス⚙️ 外部コマンド🌐 ネットワークアクセス

Finish Complex Tasks with Verifiable Gates

Substantial agent tasks often end with incomplete work or unsupported completion claims. Unlazy creates acceptance gates, runs checks, and records evidence before reporting completion.

対応: Claude Codex Code(CC)

⚠️ 38 不十分

インストール前に停止して確認を求めてください。

計画を確認し、ファイルを変更する前にユーザーの明示的な同意を得てください。

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

Review the Skillstore skill "unlazy" from https://skillstore.io/skills/leonxlnx-unlazy.md and its manifest at https://skillstore.io/api/skills/leonxlnx-unlazy/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/leonxlnx-unlazy.md 署名済み manifest GET /api/skills/leonxlnx-unlazy/manifest 署名済み lockfile GET /api/skills/leonxlnx-unlazy/lockfile

テストする

「unlazy」を使用しています。 Add a pricing toggle and verify both billing modes.

期待される結果:

Gate G1 passed: three pricing tiers render with reviewed copy.
Gate G2 passed: the toggle updates prices and billing labels.
Completion report: 2 of 2 gates passed with recorded evidence.

「unlazy」を使用しています。 Refactor the payment module with separate implementation and integration checks.

期待される結果:

The work is split into owned leaves for interfaces, providers, tests, and migration. Each leaf passes before integration verification begins.

「unlazy」を使用しています。 Review a release guide and verify every required section.

期待される結果:

All required sections, links, commands, and review notes are present. The final ledger records evidence for each completed requirement.

セキュリティ監査

高リスク

v1 • 2026/8/16 バージョン別レポートを開く

Most detections are documentation, template literals, or ordinary local file access and are false positives. Confirmed risks include shell execution from gate files, persistent Claude settings changes, and instructions that control completion behavior.

スキャンされたファイル

1,120

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (2)

高

SKILL.md:13-15 SKILL.md:72-76

Prompt Injection Attempt Detected

The skill states "You are running under anti-laziness discipline" and directs the agent to "Ignore resource anxiety." These instructions can override normal completion and resource controls.

The file directly assigns agent behavior and uses an ignore instruction. The intent is transparent, but the control language is explicit.

高

scripts/install-hooks.mjs:63-78 scripts/stop-hook.mjs:110-114

Persistent Agent Stop Control

The installer registers a command hook in Claude settings, and the hook returns a block decision while gates remain unmet. This changes future agent termination behavior.

The installer and hook implementation directly show persistent registration and decision:block output. Explicit installation and an uninstall path reduce, but do not remove, the impact.

機能レビュー項目 (11)

これらは、このスキルに期待される可能性のある実際のローカル機能であるため、レビューが必要ですが、確認済みの悪意ある動作としてはカウントされません。

高

scripts/gate-check.mjs:15

Node.js child_process module

import { spawnSync } from "node:child_process";

The child_process import is used by this script to execute CHECK values parsed from gate files. This creates a real external-command capability.

高

scripts/gate-check.mjs:120

Synchronous spawn

const res = spawnSync(gate.check, {

The script passes gate.check directly to spawnSync with shell mode enabled. A malicious or mistaken CHECK line can therefore execute arbitrary shell commands.

高

scripts/install-hooks.mjs:9

Hidden file in home directory

// node install-hooks.mjs --global install into ~/.claude/settings.json

The documented --global mode targets ~/.claude/settings.json and installs a hook affecting every project. It is opt-in, but its home-directory scope is security-relevant.

中

scripts/install-hooks.mjs:66

Ruby/shell backtick execution

command: `node "${hookScript}"`,

This line creates a persistent Claude Code command hook that runs stop-hook.mjs. The path is deterministic and quoted, but installing executable hooks changes future agent behavior.

中

scripts/install-hooks.mjs:58

Synchronous file operations

writeFileSync(target, JSON.stringify(settings, null, 2) + "\n");

The uninstall path rewrites a Claude settings file after removing matching hook entries. This is intentional configuration modification, although it requires an explicit script invocation.

中

scripts/install-hooks.mjs:78

Synchronous file operations

writeFileSync(target, JSON.stringify(settings, null, 2) + "\n");

The installer writes a command hook into project or global Claude settings. This persistent configuration change is intentional but security-relevant.

中

scripts/install-hooks.mjs:4

Hidden file access

// Default target: <cwd>/.claude/settings.local.json (personal, per-project,

The default installer target is the project-local .claude/settings.local.json file. Modifying agent configuration is intentional and disclosed, but it changes harness behavior.

中

scripts/install-hooks.mjs:9

Hidden file access

// node install-hooks.mjs --global install into ~/.claude/settings.json

The --global option deliberately accesses ~/.claude/settings.json to register the Stop hook. Explicit invocation reduces risk but does not remove the persistent configuration impact.

中

SKILL.md:25-27

Ruby/shell backtick execution

```

The fenced example instructs the agent to run gate-check.mjs, which executes CHECK values through a shell. The command is documented rather than automatic, but the execution capability is real.

中

SKILL.md:96-98

Ruby/shell backtick execution

```

This fenced block introduces the optional install-hooks.mjs command. Running it modifies Claude Code settings and registers an executable Stop hook.

中

SKILL.md:98-100

Ruby/shell backtick execution

```

The cited block contains the install-hooks.mjs invocation. It is explicitly optional, but execution persists a hook in Claude Code configuration.

リスク要因

📁 ファイルシステムへのアクセス (26)

⚙️ 外部コマンド (35)

🌐 ネットワークアクセス (4)

README.md:49 README.md:55 README.md:77 SKILL.md:7

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/leonxlnx-unlazy/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/leonxlnx-unlazy/security.svg)](https://skillstore.io/skills/leonxlnx-unlazy?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/leonxlnx-unlazy?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/leonxlnx-unlazy/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/leonxlnx-unlazy.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

leonxlnx. (2026). unlazy security audit report (audit version 1) [Author version 2.0.0]. Skillstore. https://skillstore.io/skills/leonxlnx-unlazy/audits/1

BibTeX形式の引用

@techreport{leonxlnx-leonxlnx-unlazy-2026,
  author = {leonxlnx},
  title = {unlazy security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/leonxlnx-unlazy/audits/1},
  note = {Author version 2.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "unlazy security audit report (audit version 1)"
version: "2.0.0"
type: report
authors:
  - name: "leonxlnx"
date-released: "2026-08-16"
url: "https://skillstore.io/skills/leonxlnx-unlazy/audits/1"
identifiers:
  - type: other
    value: "skillstore:leonxlnx-unlazy:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

100

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Verify a Feature Delivery

Define behavioral checks, run them after implementation, and record evidence before marking the feature complete.

Coordinate a Large Refactor

Split work into owned leaves, define shared contracts, and verify integration at each branch.

Audit a Documentation Release

Track required sections, links, examples, and review evidence in one completion ledger.

これらのプロンプトを試す

Create Basic Gates

Use unlazy for this task. Create a GATES.md file with clear outcomes, complete the work, and show evidence for every gate.

Run Verifiable Checks

Create acceptance gates for [task]. Add safe CHECK and EXPECT lines where possible. Review every command with me before execution.

Decompose a Subsystem

Use tree 4 for [subsystem]. Define contracts and file ownership first. Create leaf gates, complete each leaf, then verify integration gates.

Orchestrate a Full Build

Plan [project] in orchestrated mode. Assign disjoint leaves, define branch gates, rerun every child check, and audit all reported numbers before completion.