@xalia/agent 0.5.0

package/test_data/background_test_script.json

@@ -0,0 +1,11 @@
+[
+  {
+    "index": 0,
+    "message": {
+      "role": "assistant",
+      "content": "This is a generated message for testing purposes",
+      "tool_calls": []
+    },
+    "finish_reason": "stop"
+  }
+]

package/test_data/dummyllm_script_simplecalc.json

@@ -0,0 +1,28 @@
+[
+  {
+    "index": 0,
+    "message": {
+      "role": "assistant",
+      "content": "I'll help you divide those numbers. Let me calculate 12341543 divided by 431234132.",
+      "tool_calls": [
+        {
+          "id": "toolu_017umizET2MjAC2ir5t4iiVR",
+          "type": "function",
+          "function": {
+            "name": "sudomcp_simplecalc__divide",
+            "arguments": "{\"a\": 12341543, \"b\": 431234132}"
+          }
+        }
+      ]
+    },
+    "finish_reason": "tool_calls"
+  },
+  {
+    "index": 0,
+    "message": {
+      "role": "assistant",
+      "content": "The result of dividing 12341543 by 431234132 is approximately 0.0286 (or about 1/35)."
+    },
+    "finish_reason": "stop"
+  }
+]

package/test_data/git_message_profile.json

@@ -0,0 +1,4 @@
+{
+  "system_prompt": "Scan a code diff and produce concise and accurate commit messages.  The messages should be of the form:\n```\nfeat: added some feature\n```\nOR\n```\nfeat[component]: added some feature\n```\nand ideally be contained on a single line.  Instead of `feat`, `fix`, `wip` and `chore` are acceptable tags. Look at file paths and directories for clues regarding which components are being modified. NEVER explain any intermediate steps. Output ONLY the raw message.\n",
+  "mcp_settings": {}
+}

package/test_data/git_wip_system.txt

@@ -0,0 +1,5 @@
+Your job is to look at WIP code changes and create a brief but informative description of:
+- the high level code change being made
+- the parts that have been completed
+- suggestions for what should be tackled next
+I will read the description on Monday morning to refresh my memory.  I'll have forgotten some important details, but will still have the broad goals in mind (you can leverage this to keep the description short).  I want to get the context back into my mind as quickly as possible.

package/test_data/pr_message_profile.json

@@ -0,0 +1,4 @@
+{
+  "system_prompt": "Scan a set of git commits and generate a concise pull-request description.  If the PR covers multiple concepts, include a bullet list of the form:\n```\n- [ ] Add some feature to some component\n...\n```\nLeave the checkbox empty so the user can fill it in when complete.\nNEVER explain any intermediate steps. Output ONLY the raw message.\n",
+  "mcp_settings": {}
+}

package/test_data/pr_review_profile.json

@@ -0,0 +1,4 @@
+{
+  "system_prompt": "Scan a set of diffs and create a PR review with the following format:\n```\n## <filename>:<line-number>\n\n<description of the issue>\n\n```\n\nCheck for maintainability issues, unnecessary complexity etc.\n",
+  "mcp_settings": {}
+}

package/test_data/prompt_simplecalc.txt

@@ -0,0 +1 @@
+What is 12341543 divided by 431234132?

package/test_data/simplecalc_profile.json

@@ -0,0 +1,4 @@
+{
+  "system_prompt": "You are a helpful agent",
+  "mcp_settings": {"sudomcp_simplecalc":["divide"]}
+}

package/test_data/sudomcp_import_profile.json

@@ -0,0 +1,4 @@
+{
+  "system_prompt": "Your job is to parse the public README of an mcp server code repository and extract the commands to run the server. You must then create a yaml \"sudomcp\" spec of the form:\n```\nname: mongodb-local\ntitle: MongoDB Local\ndescription: Interact with a local MongoDB instance (via connection string)\nlogo_url: \"https://github.com/sudobase-ai/mcp-servers/blob/master/mongodb-local/logo.png?raw=true\"\nconfig_schema:\n  connection_string:\n    type: string\n    default: \"mongodb://localhost\"\nstdio_server_params:\n  command: \"npx\"\n  args:\n    - \"-y\"\n    - \"mongodb-mcp-server\"\n  env:\n    MDB_MCP_CONNECTION_STRING: $connection_string\n```\nThe above is for a mongodb MCP server, requiring an environment variable `MDB_MCP_CONNECTION_STRING`. The `config_schema` section determines the variables that are required from the user in order to populate the `args` or the `env` values. Each server will have its own configuration requirements and some servers will not require a `config_schema` section at all.  The use of \"mcp\" in the name, title and description is redundant and should be avoided.\n\nDo not explain any intermediate steps or give any justification.  Just output the yaml file directly so I can pipe it to a file.  No ``` or similar notation.\n\n",
+  "mcp_settings": {"duckduckgo-search":["fetch_content"]}
+}

package/test_data/test_script_profile.json

@@ -0,0 +1,8 @@
+{
+  "NOTES": "Intended to be used by the mcppro test_script",
+  "model": "dummy:test_data/dummyllm_script_simplecalc.json",
+  "system_prompt": "You are a helpful agent",
+  "mcp_settings": {
+    "sudomcp_simplecalc":["add","divide"]
+  }
+}

package/tsconfig.json

@@ -0,0 +1,13 @@
+{
+  "compilerOptions": {
+    "target": "es2020",
+    "module": "NodeNext",
+    "moduleResolution": "NodeNext",
+    "resolveJsonModule": true,
+    "skipLibCheck": true,
+    "outDir": "dist",
+    "strict": true,
+    "esModuleInterop": true
+  },
+  "include": ["src/**/*.ts"],
+}