Repository navigation
feat(integrations): a setup skill that proves pasu is in the path - #114
Open
CharmingGroot wants to merge 1 commit into
Open
CharmingGroot wants to merge 1 commit into
CharmingGroot wants to merge 1 commit into
Conversation
A pasu that is running but not in the path looks healthy and checks nothing (the proxy-bypass gap found in the opencode E2E). The skill walks an operator from finding where the agent's LLM traffic goes to wiring the right front-end, and ends with a probe through the agent's own base URL: an embeddings call must come back as pasu's 403, not the provider's answer. It is onboarding, not a guard. A skill is instructions to a model, and a model under prompt injection can ignore them, so it decides nothing. Signed-off-by: Ho Geun Choi <ohyes9711@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked on #113.
integrations/skills/pasu-setup/is an agent skill that switches pasu on. It is onboarding, not a guard: a skill is instructions to a model, a model under prompt injection can ignore them, and so every decision stays in the pasu process and the kernel layer. The skill says so itself.What it does
rules.yamlfromdefault: denyand the agent's declared tools, then asks the user about eachask/deny.integrations/examples. It names the settings that must not change, and the three Envoy Gateway settings that switch pasu off silently.pasu_policy_block), not the provider's answer.processingModeleft out orshadowModeon.The probe was checked against the binary: through pasu it got a 403
pasu_policy_block; the same request direct to the provider got a 200.Install
Copy the directory into
~/.claude/skills/or a project's.claude/skills/. This is documented inintegrations/README.md.Agent-specific hooks (Claude Code, opencode) are deliberately left out.
CLAUDE.mdkeeps per-framework hooks off pasu's path.🤖 Generated with Claude Code