Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/configflux/weldWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/hooks/configflux/weld/session-start)<a href="https://agentmods.dev/hooks/configflux/weld/session-start"><img src="https://agentmods.dev/badge/hooks/configflux/weld/session-start/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/hooks/configflux/weld/session-start"><img src="https://agentmods.dev/badge/hooks/configflux/weld/session-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
SessionStart scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"SessionStart": [
{
"description": "Refresh the demo agent graph at session start; rollback by deleting .weld/agent-graph.json.",
"matcher": "",
"hooks": [
{
"command": "wd agents discover",
"type": "command"
}
]
}
]
}What else settings.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 14 lines scan A e8decb56bed4
SessionStart is a hook published in the GitHub repository configflux/weld (6 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: a hook is shell that never enters the context. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other hooks, from other repositories
PreToolUse
Runs before the agent uses a tool for Grep, Glob, Bash and Read tool calls, running frigg hook pretooluse. From bnomei/frigg.
SessionStart
Runs when a session starts on startup, resume, clear and compact, executing readiness.sh. From styler-ai/ProjectAtlas.
SubagentStop
Runs when a subagent finishes, executing run.sh via sh. From Digital-Threads/token-pilot.
SessionStart
Runs when a session starts, executing jarvis-index-status.sh. From jarvis-intelligence/jarvis-index.
SessionStart
Runs when a session starts on startup, executing install_pkgs.sh. From supabase/supabase.
PostToolUse
Runs after a tool call finishes for Write and Edit tool calls, executing format_and_lint.sh. From supabase/supabase.