Question 1

What does VTTForge command protection cover?

Accepted Answer

Reviews VTTForge CLI commands that write a project: the scaffold, lint fixes, and the v14 migration written in place. The audit, the lint report and the migration preview stay unreviewed. The listing declares 3 rules and 3 permission checks. 3 operations · 3 reviewed by default. Coverage is limited to these reviewed operations and the surrounding Guard policy.

Question 2

Is VTTForge command protection active by default?

Accepted Answer

External · opt-in: External coverage. It must be enabled through Guard controls; this page does not activate it. Enabling state is always controlled through Guard policy, never from this directory.

Question 3

Who maintains VTTForge command protection?

Accepted Answer

This listing entered the catalog as a community contribution through a public pull request with recorded provenance. Credit is attribution only. A verified publisher profile and the claim flow verify authority separately; neither is an upstream endorsement or a HOL safety certification.

Question 4

Is a listing of VTTForge command protection a security guarantee?

Accepted Answer

No. Every listing documents source, activation model, maintainer identity, and stated limitations so you can evaluate coverage before enabling it. Review the stated limitations and the exact source tree before relying on any single control.

Question 5

Which commands does VTTForge command protection allow or review by default?

Accepted Answer

3 operations · 3 reviewed by default. Examples: vttforge init (reviewed by default); vttforge lint --fix (reviewed by default); vttforge migrate --write (reviewed by default). These are catalog defaults, not your workspace policy.

Question 6

How do I enable or disable VTTForge command protection?

Accepted Answer

External coverage. It must be enabled through Guard controls; this page does not activate it. Enablement is managed through your workspace's Guard policy and controls — never from this directory. Open the install guidance for the setup flow, then adjust the command coverage for command.vttforge in Guard's policy surface.

Question 7

What happens when VTTForge command protection blocks a command?

Accepted Answer

The matching action is stopped at Guard's pre-action boundary before it executes, and the decision is recorded with evidence your workspace can review. Exact behavior follows your Guard policy combined with this entry's 3 rules and 3 permission checks.

Question 8

Does evaluating VTTForge command protection send my data anywhere?

Accepted Answer

No. Guard is local-first: interception, decisions, and evidence stay on your machine unless your workspace explicitly configures cloud features. This page is documentation only — it never executes a command or changes protection state.

Question 9

Which AI coding agents does VTTForge command protection work with?

Accepted Answer

Guard runs locally alongside the major AI coding agents and MCP-capable harnesses, so this coverage applies wherever Guard intercepts actions. See the supported harness guides at https://hol.org/guard/harnesses for per-tool approval behavior and limitations.

Question 10

How much does Guard cost?

Accepted Answer

Guard has a free local tier that includes command interception, evidence, and the policy controls this listing documents. Team plans add shared policy, review queues, and audit surfaces. Current plans: https://hol.org/guard/pricing

Question 11

How do I report an incorrect or outdated VTTForge command protection listing?

Accepted Answer

Open an issue or pull request against the hol-guard repository, where the canonical catalog lives: https://github.com/hashgraph-online/hol-guard Listings are corrected through the same public review process that adds them.

Question 12

Can I get coverage for my own tool?

Accepted Answer

Yes. Community extensions are merged through public pull requests with recorded provenance, and you can claim the publisher page for a contribution you maintain through the Publisher Studio.

Question 13

How do I audit what VTTForge command protection actually enforces?

Accepted Answer

The command mapping table is the audit trail for covered commands and catalog default floors. Pair it with the reviewed rule and permission counts, the per-tool state mapping, and the exact source tree linked from View exact source at the reviewed commit. Guard records enforcement decisions with evidence locally, so what ships matches what you reviewed.

Commands	Default	Severity	Operation
`vttforge init`	Reviewed Guard intercepts the command for review before it runs.	Medium	VTTForge project scaffold Default floor Reviewed by default. Guard intercepts the command for review before it runs. Detector mode review What it matches Identifies `vttforge init`, which writes a new Foundry VTT system or module tree into the working directory, then runs the package manager install and `git init` unless --no-install and --no-git are present. A vttforge invocation whose subcommand is an unresolved shell expansion, with no literal --fix or --write beside it, is reviewed here too, since it may expand into init. Documented safe variants `VTTForge project scaffold helpVTTForge lint subcommandVTTForge migrate subcommandVTTForge audit subcommandVTTForge line with a literal --fixVTTForge line with a literal --write`skip this operation when they are the documented preview or help form. Permission ID command.vttforge.permission.init
`vttforge lint --fix`	Reviewed Guard intercepts the command for review before it runs.	Medium	VTTForge lint with fixes written Default floor Reviewed by default. Guard intercepts the command for review before it runs. Detector mode review What it matches Identifies `vttforge lint --fix`, which rewrites source files in place with the bundled formatter and linter fixes. Without --fix the command only reports. A lint invocation carrying an unresolved shell expansion is reviewed too, since it may expand to --fix. A literal --fix is reviewed whatever the subcommand token, since an expanded subcommand may be lint. Documented safe variants `VTTForge lint with fixes written help`skip this operation when they are the documented preview or help form. Permission ID command.vttforge.permission.lint-fix
`vttforge migrate --write`	Reviewed Guard intercepts the command for review before it runs.	Medium	VTTForge migration written to the project Default floor Reviewed by default. Guard intercepts the command for review before it runs. Detector mode review What it matches Identifies `vttforge migrate --write`, which rewrites a v13 Foundry VTT project for v14 in place, and with --data-models or --sheets also writes generated files next to the originals. Without --write the command previews the same edits and writes nothing. A migrate invocation carrying an unresolved shell expansion is reviewed too, since it may expand to --write. A literal --write is reviewed what… Documented safe variants `VTTForge migration written to the project help`skip this operation when they are the documented preview or help form. Permission ID command.vttforge.permission.migrate-write

VTTForge command protection

What this coverage does

Key facts

Stated limits

Command mapping

Tool state mapping

Runtime identity

Action classes

No independent profile published

Frequently asked questions