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 skills add TheophilusChinomona/claude-openclaw-plugin --skill openclaw-tender-workspacegit clone --depth 1 https://github.com/TheophilusChinomona/claude-openclaw-pluginWrote 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/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-tender-workspace)<a href="https://agentmods.dev/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-tender-workspace"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-tender-workspace/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/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-tender-workspace"><img src="https://agentmods.dev/badge/skills/theophiluschinomona/claude-openclaw-plugin/openclaw-tender-workspace.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00096 | $0.02337 |
| Opus 5 | $0.00048 | $0.01169 |
| Sonnet 5 | $0.00019 | $0.00467 |
| Haiku 4.5 | $0.00010 | $0.00234 |
Grade A, and why
openclaw-tender-workspace 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Tender Workspace Setup
Build a production-ready multi-agent tender management workspace for a construction, engineering, or professional services company. Based on the proven Tripli Tender Team architecture.
What This Skill Creates
A complete OpenClaw workspace with 5 agents that autonomously discover, analyse, draft, and compliance-check government tenders:
workspace-{client}/ ← Main workspace
├── SOUL.md ← Orchestrator agent (main WhatsApp contact)
├── AGENTS.md ← Delegation workflows
├── HEARTBEAT.md ← Periodic health checks
├── IDENTITY.md, USER.md, TOOLS.md
│
├── agents/ ← Subagent workspaces
│ ├── scout/ (SOUL.md, AGENTS.md, skills/) ← Portal scanning
│ ├── filter/ (SOUL.md, AGENTS.md, skills/) ← Suitability scoring
│ ├── architect/ (SOUL.md, AGENTS.md, skills/) ← Proposal drafting
│ └── auditor/ (SOUL.md, AGENTS.md, skills/) ← Compliance checking
│
├── skills/ ← Shared skills (briefing, pipeline, certificates)
├── scripts/ ← Utility scripts (PDF, email, downloads)
├── bid-library/ ← Company knowledge
├── compliance/ ← Certificate data
├── opportunities/ ← Per-tender folders
├── partnerships/ ← JV/subcontractor data
├── pricing/ ← Rates and models
├── registers/ ← Pipeline register
└── openclaw.json ← Multi-agent config
Setup Flow
Step 1: Gather Client Information
Ask the user for (or find in the project):
Required:
- Company legal name and trading name
- CIDB grading and categories (e.g., 6CE/6EP/6ME)
- B-BBEE level and ownership details
- Core disciplines and capabilities
- Target tender portals (eTenders, CIDB, municipal, etc.)
- Contact person for GO/NO-GO decisions (name, email, phone)
- Email address for tender briefings
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 207 lines · 96 tokens per session scan A e2e9332b4822
openclaw-tender-workspace is a skill published in the GitHub repository TheophilusChinomona/claude-openclaw-plugin (2 stars, last pushed 5mo ago), licensed MIT. It adds 96 tokens to every session and 2,337 once invoked, about $0.0005 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.