Run any Skill in Manus with one click

sandbox-hardening

Stars0

Forks1

UpdatedMay 5, 2026 at 00:04

Use when changing shell execution, filesystem writes, path permissions, network access, bubblewrap policies, worktree isolation, secret redaction, approval modes, or CI/headless execution safety.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

lemon07r

lemon07r/VeraCode

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

SKILL.md

readonly

name	sandbox-hardening
description	Use when changing shell execution, filesystem writes, path permissions, network access, bubblewrap policies, worktree isolation, secret redaction, approval modes, or CI/headless execution safety.

Sandbox Hardening

Prefer layered defenses.

Steps

Identify the action risk.
Resolve permission: allow, ask, or deny.
Check path scope before execution.
Apply worktree isolation for edits.
Use bubblewrap on Linux when enabled.
Redact secrets in logs.
Add tests for deny and ask paths.

Sensitive defaults

Deny .env*, private keys, token caches, SSH material, and cloud secrets unless the user explicitly overrides.

More from this repository

same repository

golang-modernize

lemon07r/VeraCode

Continuously modernize Golang code to use the latest language features, standard library improvements, and idiomatic patterns. Use this skill whenever writing, reviewing, or refactoring Go code to ensure it leverages modern Go idioms. Also use when the user asks about Go upgrades, migration, modernization, deprecation, or when modernize linter reports issues. Also covers tooling modernization: linters, SAST, AI-powered code review in CI, and modern development practices. Trigger this skill proactively when you notice old-style Go patterns that have modern replacements.

2026-05-050

golang-testing

lemon07r/VeraCode

Provides a comprehensive guide for writing production-ready Golang tests. Covers table-driven tests, test suites with testify, mocks, unit tests, integration tests, benchmarks, code coverage, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, memory leaks, CI with GitHub Actions, and idiomatic naming conventions. Use this whenever writing tests, asking about testing patterns or setting up CI for Go projects. Essential for ANY test-related conversation in Go.

2026-05-050

context-curator

lemon07r/VeraCode

Use when selecting, compacting, or reviewing repository context for an implementation, review, or investigation task. Helps build high-signal context packs from file trees, diffs, symbols, tests, docs, slices, and search hits while avoiding noisy full-repo reads.

2026-05-050

docs-steward

lemon07r/VeraCode

Use when adding, removing, or changing permanent documentation, architecture decisions, examples, CLI commands, configs, skill docs, or maintenance guidance. Keeps docs indexed, non-duplicative, and useful for future agents.

2026-05-050

eval-runner

lemon07r/VeraCode

Use when changing prompts, tools, context packing, provider behavior, permissions, subagents, search, or other agent quality-sensitive logic. Guides focused tests, SanityHarness runs, metric capture, and adoption decisions.

2026-05-050

prompt-lab

lemon07r/VeraCode

Use when editing base prompts, tool descriptions, skill descriptions, subagent prompts, compaction summaries, or prompt wording experiments such as soft vs hard rules, compact language, mood, or persona framing.

2026-05-050

Run any Skill with one click