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.
npx agentmods add agents/orieg/gws-connector/workspace-contextgit clone --depth 1 https://github.com/orieg/gws-connectorWrote 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/agents/orieg/gws-connector/workspace-context)<a href="https://agentmods.dev/agents/orieg/gws-connector/workspace-context"><img src="https://agentmods.dev/badge/agents/orieg/gws-connector/workspace-context.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00053 | $0.00096 |
| Opus 5 | $0.00026 | $0.00048 |
| Sonnet 5 | $0.00011 | $0.00019 |
| Haiku 4.5 | $0.00005 | $0.00010 |
Grade A, and why
gws-workspace-context 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 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
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
Read and follow the instructions in CONTEXT.md for all GWS workspace operations — it contains the account routing rules, per-service guidelines, and safety requirements.
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.
- 4d ago First seen · 7 lines · 53 tokens per session scan A 8579ec9de32c
gws-workspace-context is an agent published in the GitHub repository orieg/gws-connector (1 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 96 once invoked, about $0.0003 per session on Opus 5. 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 agents, from other repositories
iteration-guard
The verify gate of the Logic-Lens iteration loop. Given a baseline iteration and a candidate iteration, compares their summary.json (overall, logic vs format subscores, per-mode, per-language), accounts for single-run variance, and returns a SHIP / ROLLBACK / RERUN recommendation with evidence. Use after…
skill-editor
Applies a single, minimal, generalized edit to a Logic-Lens skill (SKILL.md / guide / shared file) given a concrete failure diagnosis. Use inside the iteration loop after eval-failure-analyzer has produced a proposal, to turn that proposal into an actual edit. Mutates files; does NOT run evals or sync the cache — it…
eval-failure-analyzer
Analyze Logic-Lens benchmark/eval failures. Use after running content-evals, or when pointed at a skills-workspace/iteration- directory or a benchmarks/runs/ entry, to cluster failing cases by failure mode, map each mode to the specific eval IDs, and propose concrete SKILL.md disambiguation-rule changes. Read-only…
error-analyzer
Analyze multiple PostHog errors in parallel to identify patterns, root causes, and prioritize fixes based on user impact.
discovery-to-fr
End-to-end research-to-spec workflow. Takes raw user research and produces a complete Feature Request with persona context — running synthesize-user-research, build-user-persona, and write-feature-request in sequence. Use when you have research data and want to go straight to a finished FR without managing each skill…
sprint-to-stakeholders
Full sprint-to-communications workflow. Takes sprint data and produces all three stakeholder artefacts — running sprint-review, write-release-notes, and write-stakeholder-update in sequence. Use at the end of every sprint to produce the complete communication package in one run. Trigger on: "run…