bdi-mental-states
An agent skill by muratcankoylan, from muratcankoylan/Agent-Skills-for-Context-Engineering. Tags: api, automation, developer-tools, legal, strategy.
What it does
This skill should be used when modeling agent mental states with BDI concepts: beliefs, desires, intentions, RDF-to-belief transformations, rational agency traces, cognitive agents, BDI ontologies, and neuro-symbolic AI integration.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add muratcankoylan/Agent-Skills-for-Context-Engineering --skill bdi-mental-states
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering
cp -r Agent-Skills-for-Context-Engineering/skills/bdi-mental-states ~/.claude/skills/bdi-mental-states
Safety box score
Grade A, minimal risk: 0 of 100 risk points, rated 2026-10-19. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is markdown-only guidance for modeling BDI mental states with Turtle/SPARQL/Python/Java examples; it does not ship runnable scripts or installers. The main practical risk is only if a downstream user copies the example code, which can connect to SPARQL endpoints or LLM services, but the skill itself does not execute anything or touch secrets.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 0 (none) | No native scripts or executable files are shipped; the repository contents are Markdown documentation and code examples only. |
| Network access | 0 (none) | The skill names external namespaces and example endpoints, but it does not include code that actually fetches remote content or sends data off-machine. |
| Filesystem reach | 0 (none) | There are no commands or scripts that read, write, or delete files outside the project; no dotfile or system-path access is described. |
| Secrets & credentials | 0 (none) | The skill does not mention tokens, passwords, key stores, `.env` files, or browser/CLI sessions. |
| Privilege & persistence | 0 (none) | No sudo, service registration, global installs, or shell/OS configuration changes are present. |
| Instruction hijack surface | 0 (none) | There is normal modeling guidance and prompt text like 'You are a BDI mental state modeler,' but nothing that tells the agent to ignore rules, hide actions, or follow untrusted remote instructions. |
| Irreversible actions | 0 (none) | The skill discusses beliefs, desires, intentions, and plan execution conceptually, but it does not itself send messages, deploy, publish, pay, or delete anything. |
| Transparency | 0 (none) | All shipped content is readable Markdown; there are no binaries, base64 blobs, decoded-at-runtime code, or unpinned installs. |
Before installing
- Nothing to execute here: verify the skill folder contains only Markdown/reference files.
- If you plan to reuse the example code, sandbox any SPARQL endpoint and LLM client before pointing it at real data.
- Review any downstream use of the external ontology URLs and namespaces before enabling network access.
Rated 2026-10-19 by an automated review of 5 files from the skill's repository.
Source
- Repository
- muratcankoylan/Agent-Skills-for-Context-Engineering (all skills from this repository)
- Path
- skills/bdi-mental-states/SKILL.md
- Branch
- main
- Updated
- 2026-09-19
Related skills
- memory-systems — This skill should be used for persistent semantic memory in agent systems: cross-session knowledge retention, entity tracking, temporal validity.
- tool-design — This skill should be used for the tool-interface layer of an agent system specifically: writing tool descriptions agents can route on.
- legacy-modernizer — Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps.
- context-compression — This skill should be used when long-running agent sessions need context compression, structured summarization, compaction, token-per-task optimization.
- context-degradation — This skill should be used for diagnosing and mitigating context degradation: lost-in-middle failures, context poisoning, context clash, context confusion.
- context-engineering-collection — A comprehensive collection of Agent Skills for context engineering, harness engineering, multi-agent architectures, and production agent systems.