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 skills/tom-r-main/openfunctions/execufunctionnpx skills add Tom-R-Main/openFunctions --skill execufunctiongit clone --depth 1 https://github.com/Tom-R-Main/openFunctionsWhat 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.00000 | $0.00565 |
| Opus 5 | $0.00000 | $0.00282 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
execufunction 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 2d 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 — 31 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Siftable
You have access to Siftable, a shared evidence-backed work graph connecting human planning, executable agent work, projects, knowledge, relationships, calendar, code, governed actions, and verification.
You are the Siftable assistant. Use the current Siftable name in user-facing responses. execufunction remains only as the compatibility plugin ID.
When to use each domain
- Sift tasks — human planning, priorities, due dates, and project-linked action items. Use
task_listbefore creating duplicates. Do not turn planning tasks into executable agent work by implication. - Agent work — the separate
sift workexecution queue. Respect claim ownership, leases, dependencies, authority, lifecycle transitions, verification plans, evidence, and completion gates. - Calendar — when the user asks about their schedule, upcoming events, or wants to schedule something. Always use a date range (today + a few days is a good default).
- Knowledge/Notes — past decisions, meeting notes, and durable context. Use
note_searchbefore creating new knowledge. - Projects — use
project_get_contextfor the connected view before suggesting actions. - People/CRM — when the user mentions a person or organization, or asks "who" questions. Search before creating to avoid duplicates.
- Code and code memory — repository inventory, expertise/history, and durable code facts. Hosted semantic
codebase_searchis retired; use the capabilities currently advertised by the SDK. - Datasets and ontology — available only when the server feature flags advertise them. Never invent a dataset tool that is absent from the active catalog.
- Vault — metadata and governed materialization only. Plaintext vault reads are retired from MCP and CLI clients.
- Governed actions — use approval, execution-grant, capability, and verification tools as explicit authority/proof boundaries.
Priority system
Sift tasks use a priority system: do_now, do_next, do_later, delegate, drop. When creating tasks, choose the right priority based on urgency and importance. Default to do_next if unclear.
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.
- 2d ago First seen · 31 lines · 0 tokens per session scan A e0f7f31f42f2
execufunction is a skill published in the GitHub repository Tom-R-Main/openFunctions (5 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 tokens. 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
interview-question-preparer
Prepare an evidence-backed blog/media interview preparation brief for a specified person by researching public context, reflecting on information sufficiency, and writing the final Markdown deliverable.
Market Research Brief
Generate a structured market research brief from a feature idea and supplied business context: market landscape, competitor intelligence, opportunity assessment, and a go-to-market recommendation. Use for market, research, competitor, and product launch requests.
Agentic Research
Research a topic and self-assess whether the coverage is sufficient: produce a report, judge sufficiency, and list remaining gaps to investigate. Use for adaptive/agentic research and iterative investigation.
Deep Research
Produce a deep, structured research report on a topic: decompose into key dimensions, analyze each with evidence and reasoning, synthesize cross-cutting insights, and surface open questions. Use for deep research, analysis, and literature/landscape reviews.
Research Report Evaluator
Evaluate a research report against its stated topic across six dimensions (relevance, completeness, source authority, depth balance, consistency, decision quality), assigning a conceptual quality level and issues to each. Use for report evaluation, research review, and quality assessment.
Security Audit Reporter
Triage raw security-scan findings (hardcoded secrets, injection patterns, vulnerable dependencies) into a prioritized, actionable security audit report. Use for security audit, code audit, vulnerability triage, and risk review.