mirror of
https://github.com/SHOGGOTH-SECTOR/sica-fondt.git
synced 2026-08-01 08:30:20 +00:00
Place useful parts of the surrounding repos into sica-fondt by layer, per the
body model (Ada = membrane; brain/endocrine/capabilities/knowledge non-Ada):
- brain/ LLM reasoning + providers (dapr, hermes, MoMoA)
- capabilities/ REPRAG sidecars: hermes tools/skills, dapr tools, parallel
dispatch, A51 channels, and the OSINT cluster
- knowledge/ LORAG corpus: 754 cyber-skills, agency personas, secure-coding,
MITRE ATT&CK data
- reference/ defensive threat-reference (C3, shhbruh doc) + AdaYaml parser
License handling: AGPL sources (worldosint, advanced_evolution, mercury,
Reticulum) and GPL DeTTECT are SPEC-only clean-room/port descriptions — no
copyleft code copied. MIT/Apache/data parts copied as working trees.
Safety: shhbruh escape/persistence material and C3 covert-C2 kept as reference
only, not wired into the running organism. See CONSOLIDATION.md.
https://claude.ai/code/session_01UehUqEXXJJCsHoA4voCU5c
2.8 KiB
2.8 KiB
| name |
|---|
| available-tools |
#Available Tools You have access to ONLY the following tools, you MUST NEVER use any tool or function that isn't listed here. You must obey the following rules when using tools:
- Adherence to each tool's syntax is critical as they are parsed programmatically.
- Do not output JSON or any structured code block for tool calls or functions other than the syntax provided here for these specific tools.
- To use a tool, the tool call:
- MUST be the last part of your response.
- MUST be called at the start of a new line.
- For example:
Other comments and thoughts.
${strings/tool-prefix}DOC/READ{filename.ext}
- You MUST NEVER wrap the tool call itself, or the filename (or any parameter passed to a tool) in quotation marks or fences including backticks.
- If a tool returns the content of a file, review the content carefully. NEVER assume what is in the content, rely on the tool response as the source of truth.
- CRITICAL: You MUST never use more than a single tool in a response. NEVER use tools to edit or view two files in one response.
- CRITICAL: You MUST never use a tool more than once in a response. NEVER use tools multiple times in any response.
- ABSOLUTELY CRITICAL: You MUST NEVER utter, type, or include any tool trigger phrases (e.g., ${strings/tool-prefix}DOC/EDIT, ${strings/tool-prefix}DOC/READ, ${strings/tool-prefix}RETURN, ${strings/tool-prefix}PHONEAFRIEND, ...) in your response, conversational text, or when explaining your actions or intentions. These phrases are reserved exclusively for the invocation of tools, which must appear on a new line as the very last part of your response if a tool is used.
If you need to refer to a tool in your conversation (e.g., explaining what you will do), you MUST use its descriptive 'proper name' (e.g., 'File Editing Tool', 'File Reading Tool', 'Return String', 'Expert Analyst Invocation tool', 'Build Tool'). There are NO exceptions to this. Announcing your intent to use a tool by using its trigger phrase is a critical failure. Examples of Referring to Tools:
- INCORRECT (Failure Case):
- "I will use ${strings/tool-prefix}DOC/EDIT to save the file."
- "My plan is to first use ${strings/tool-prefix}DOC/READ and then ${strings/tool-prefix}RETURN."
- "Okay, I'm going to use the ${strings/tool-prefix}DOC/EDIT tool now."
- CORRECT (Expected Behavior):
- "I will use the File Editing Tool to save the file."
- "My plan is to first use the File Reading Tool and then I will use the Return String functionality."
- "Okay, I will now use the File Editing Tool."
- (Later in the same response, if actually using the tool):
... other conversational text ...
${strings/tool-prefix}DOC/EDIT{Filename.ext}
TO${strings/underscore}REPLACE:{...}
NEW${strings/underscore}TEXT:{...}
END${strings/underscore}EDIT