Borrowing it
Nothing to install: this file belongs to benedya/octoquery. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/benedya/octoquery/main/.agents/skills/helpdesk-demo-db/SKILL.mdgit clone --depth 1 https://github.com/benedya/octoqueryWrote 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/benedya/octoquery/helpdesk-demo-db)<a href="https://agentmods.dev/skills/benedya/octoquery/helpdesk-demo-db"><img src="https://agentmods.dev/badge/skills/benedya/octoquery/helpdesk-demo-db/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/benedya/octoquery/helpdesk-demo-db"><img src="https://agentmods.dev/badge/skills/benedya/octoquery/helpdesk-demo-db.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.00070 | $0.00500 |
| Opus 5.5 | $0.00028 | $0.00200 |
| Sonnet 5.5 | $0.00014 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
helpdesk-demo-db 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 2mo 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
Helpdesk database
The database is exposed as the MCP tool sql_helpdesk_demo. Answer questions by sending a single SQL query string (T-SQL / SQL Server dialect) to that tool. Results come back as JSON rows, truncated to the configured row limit (default 100) — use TOP, aggregation, or ORDER BY to keep result sets small and relevant.
Schema
- customers —
id,email,full_name,company - agents —
id,full_name,team(Tier 1, Tier 2) - tickets —
id,customer_id→ customers,agent_id→ agents (NULL = unassigned),subject,priority(low,medium,high,urgent),status(open,pending,resolved,closed),created_at,resolved_at(NULL until resolved/closed)
Relations
- One customer has many tickets (
tickets.customer_id→customers.id). - One agent handles many tickets (
tickets.agent_id→agents.id);agent_id IS NULLmeans the ticket is not assigned yet.
Conventions
- Dialect is T-SQL: use
TOP n(notLIMIT),GETDATE()for now,DATEDIFF(hour, created_at, resolved_at)for durations. - A ticket is outstanding when
status IN ('open', 'pending');resolvedandclosedare finished. - Resolution time only makes sense where
resolved_at IS NOT NULL. - "Backlog" questions usually mean outstanding tickets grouped by priority; urgent unassigned tickets (
priority = 'urgent' AND agent_id IS NULL) are the ones worth flagging.
Guidelines
- Treat the database as read-only: stick to
SELECTunless the user explicitly asks to modify data. - Prefer one well-formed query over many small ones; use joins and aggregates server-side.
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.
- 2mo ago First seen · 32 lines · 70 tokens per session scan A f5d7a2b57d1d
helpdesk-demo-db is a skill published in the GitHub repository benedya/octoquery (3 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 500 once invoked, about $0.0003 per session on Opus 5.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.
helpdesk-demo-db compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| helpdesk-demo-dbbenedya/octoquery | Skill | 3 | 3mo ago | MIT | A | 70 | Claude Code, Codex |
| omh-relational-dbrlaope/oh-my-hermes | Skill | 5.2k | yesterday | MIT | A | 100 | Claude Code, Codex |
| redteam-sqli-detail-packNetw0rkNoob/VulnClaw | Skill | 3.9k | 8d ago | MIT | A | 59 | Claude Code, Codex |
| api-canvascyanheads/obsidian-mcp-server | Skill | 702 | 7d ago | Apache-2.0 | A | 85 | Claude Code |
| api-mirrorcyanheads/obsidian-mcp-server | Skill | 702 | 7d ago | Apache-2.0 | A | 68 | Claude Code |
| data-governanceWrongStack/WrongStack | Skill | 404 | yesterday | MIT | A | 92 | Claude Code, Codex |
| backup-recoveryWrongStack/WrongStack | Skill | 404 | yesterday | MIT | A | 87 | Claude Code, Codex |